action #13286
closedShow "assigned workers" also for incomplete jobs
0%
Description
User story¶
As a investigator of why jobs fails as incomplete I want to see which worker was used to be able to lookup system logs even when no logs could be uploaded
acceptance criteria¶
- AC1: incomplete jobs provide the information somewhere accessible over the webpage which worker was used
tasks¶
- Running jobs show e.g. "Assigned worker: openqaworker4:2", that could be extended to incomplete
Updated by coolo over 8 years ago
- Related to action #13144: show history of jobs in worker view added
Updated by mkittler about 8 years ago
- Status changed from New to Feedback
- Assignee set to mkittler
Isn't this just a duplicate of https://progress.opensuse.org/issues/6564, or am I missing something?
Updated by okurz about 8 years ago
well, originally it was not a duplicate because #6564 is not describing the same user story but I guess with your PR you are on a good way. But to fully cover the AC I would like to see a test :-)
Updated by mkittler about 8 years ago
Isn't this test sufficient: https://github.com/os-autoinst/openQA/pull/1079/commits/2856fe4e1761d73341ca929990f8547f9efa0e79
Tests:
- Setting of assigned worker in scheduler code
- Displaying assigned worker when job is running and when incomplete
Updated by okurz about 8 years ago
In https://github.com/os-autoinst/openQA/pull/1079/commits/2856fe4e1761d73341ca929990f8547f9efa0e79#diff-7b77b47860f0cd1f6dfd7aef3c62efbeR233 I see that a job is set to FAILED, i.e. done, and then checked. But I don't see a test where an actual incomplete is tested. Can you point me to one?
Updated by mkittler almost 8 years ago
- Status changed from Feedback to Resolved
There is no test where it is set to incomplete. But for the logic it doesn't matter. As far as I see, it is just relevant that the job isn't running.
And there is already a case in production where it works: https://openqa.suse.de/tests/677617#downloads