action #55415

restart "recent incompletes" or "incompletes of today" easier then over web UI

Added by okurz over 3 years ago. Updated almost 3 years ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:



Sometimes, especially when a nightly deployment breaks some stuff or wrong test settings have been applied within test settings before a new build is triggered, after a fix has been applied it is not so easy to "retrigger all related incompletes". For example #55412 is such a case where there are around 50 incompletes which need retriggering. What I use so far is to either reschedule complete builds or in this case walk over and click the retrigger button. Would be nice to have is at least one of the following alternatives

  1. a simpler query from CLI, e.g. openqa-client --host --json-output jobs latest=1 state=done result=incomplete age="<5h"
  2. batch-retrigger multiple jobs from the web UI by selecting them
  3. batch-retrigger multiple jobs based on query matches
  4. know a workaround using direct database queries
  5. query incomplete jobs based on text pattern matches in the log files

Related issues

Related to openQA Infrastructure - action #55505: lots of incompletes on o3, "qemu-system-x86_64: -vnc :91,share=force-shared: Failed to find an available port: Address already in use", maybe only openqaworker4:1?Resolved2019-08-14

Related to openQA Project - coordination #62420: [epic] Distinguish all types of incompletesResolved2018-12-12


#1 Updated by okurz over 3 years ago

  • Related to action #55505: lots of incompletes on o3, "qemu-system-x86_64: -vnc :91,share=force-shared: Failed to find an available port: Address already in use", maybe only openqaworker4:1? added

#2 Updated by okurz over 3 years ago

#55505#note-2 shows another use case using direct SQL queries to find all incompletes on a specific worker instance of a specific day.

Would it be good to somehow allow access to SQL? whitelist/blacklist certain parts? over all SQL stuff over abstracted API calls?

#3 Updated by okurz about 3 years ago

#4 Updated by okurz almost 3 years ago

  • Priority changed from Normal to Low
  • Target version set to future can help and is good enough for now. Still a nice use case to provide in an extension for the client.

Also available in: Atom PDF