action #51935

Better logging from scheduler+working why jobs are *not* picked up

Added by okurz 9 months ago. Updated 14 days ago.

Status:RejectedStart date:23/05/2019
Priority:LowDue date:
Assignee:okurz% Done:


Category:Feature requests
Target version:QA - future



A common problem that openQA newcomers hit is: "Why does openQA not pick up my scheduled jobs?". The reasons can be multiple, e.g. typo in the created job (#51932) or workers.ini, mismatch in data protocol, etc. The scheduler in "debug"-mode already gives an overview on each scheduling tick how many workers it found, how many are free, how many jobs need scheduling, etc. In case no scheduled job was assigned to a worker though more output would be helpful to find out what did not match.


#1 Updated by kraih 9 months ago

  • Assignee set to kraih

#2 Updated by kraih 9 months ago

This looks like it might overlap with my refactoring of the scheduler, so i'll give it a try.

#3 Updated by coolo 9 months ago

This might be fun to see if you have 1 worker and 1 job, but if you 3000 jobs and 300 workers, which job did not fit which worker can easily be a million line of logs - every couple of seconds.

#4 Updated by kraih 9 months ago

  • Assignee deleted (kraih)

#5 Updated by coolo 7 months ago

  • Priority changed from Normal to Low
  • Target version set to future

This would be an extra option

#6 Updated by okurz 14 days ago

  • Status changed from New to Rejected
  • Assignee set to okurz

ok, I guess this won't happen

Also available in: Atom PDF