Project

General

Profile

Actions
Copy link

action #55415

open

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

Added by okurz over 5 years ago. Updated over 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public) - future
Start date:
2019-08-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

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 https://openqa.opensuse.org/tests/?&resultfilter=Incomplete 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 https://openqa.opensuse.org --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 2 (0 open — 2 closed)

Related to openQA Infrastructure (public) - 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?Resolvedokurz2019-08-14

Actions
Related to openQA Project (public) - coordination #62420: [epic] Distinguish all types of incompletesResolvedokurz2018-12-12

Actions
Actions
Copy link
 #1

Updated by okurz over 5 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
Actions
Copy link
 #2

Updated by okurz over 5 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?

Actions
Copy link
 #3

Updated by okurz almost 5 years ago

Actions
Copy link
 #4

Updated by okurz over 4 years ago

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

https://github.com/os-autoinst/scripts/blob/master/openqa-restart-incompletes-on-worker-instance can help and is good enough for now. Still a nice use case to provide in an extension for the client.

Actions
Copy link

Also available in: Atom PDF