Actions
Feature #7917
closedTake into account configuration to distinguish sub-jobs with the same modules and rule specifications
Start date:
01/26/2017
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
During creation of a sub-jobs for tests I got the following exception:
Traceback (most recent call last):
File "/home/ubuntu/klever/core/core/core.py", line 74, in main
job.decide(self.conf, self.mqs, {'build': multiprocessing.Manager().Lock()}, self.uploading_reports_process)
File "/home/ubuntu/klever/core/core/utils.py", line 56, in callbacks_caller
ret = attr(*args, **kwargs)
File "/home/ubuntu/klever/core/core/job.py", line 79, in decide
self.get_sub_jobs()
File "/home/ubuntu/klever/core/core/utils.py", line 56, in callbacks_caller
ret = attr(*args, **kwargs)
File "/home/ubuntu/klever/core/core/job.py", line 332, in get_sub_jobs
raise ValueError('Several sub-jobs have the same identifier "{0}"'.format(sub_job_id))
ValueError: Several sub-jobs have the same identifier "/tests/linux/kernel/sched/completion/bd63ce5/linux:kernel:sched:completion"
This is because of sub-job identifiers for job class "Testing rule specifications" is concatenation of a path to tests and hash sums of modules and rule specifications.
The issue isn't important since it can be easily workarounded.
Actions