Project

General

Profile

Actions

action #124991

closed

coordination #102915: [saga][epic] Automated classification of failures

QA - coordination #94105: [epic] Use feedback from openqa-investigate to automatically inform on github pull requests, open tickets, weed out automatically failed tests

Copy ids of other investigate jobs to retry job

Added by tinita over 1 year ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-02-23
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See parent #109920.
We want to check that all investigation jobs of a failed job have finished, so we need to find out the ids of the other investigate jobs.

One solution is to save the ids in one of the investigation job.
So we create the investigation jobs for last_good_tests, last_good_build, last_good_tests_and_build, and save the job ids.
Then we create the simple retry job and add a setting to it: OTHER_INVESTIGATE_JOBS=id1,id2,id3

We choose this job because it is always created, the other investigation jobs might not always be created.

Acceptance criteria

  • AC1: The retry job has a setting mentioning the other investion job ids

Suggestions

  • This task is already complex enough for its own ticket. Getting back the id of the cloned job is not trivial, because we are using the output of the clone function already.
  • Move down the creation of the retry job to be the last clone
  • One solution is to create a partially global variable that is set by the clone function. This stops working as soon as the clone function is called as a subprocess, e.g. $(clone ...)
  • This could actually be made nicer by also moving the output of the clone function to such a helper variable. Of course we still would want to catch stderr sometimes. Needs thinking
  • Consider turning this into a perl script :]

Related issues 1 (0 open1 closed)

Copied from openQA Project - action #109920: Identify reproducible product issues using openqa-investigate size:MResolvedtinita2023-03-23

Actions
Actions #1

Updated by tinita over 1 year ago

  • Copied from action #109920: Identify reproducible product issues using openqa-investigate size:M added
Actions #2

Updated by tinita over 1 year ago

  • Subject changed from Copy ids of other investigate jobs to retry job to Copy ids of other investigate jobs to retry job size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #3

Updated by livdywan over 1 year ago

  • Subject changed from Copy ids of other investigate jobs to retry job size:M to Copy ids of other investigate jobs to retry job
  • Status changed from Workable to New

Let's re-estimate this tomorrow

Actions #4

Updated by okurz over 1 year ago

  • Category deleted (Feature requests)
  • Priority changed from High to Low

What we discussed in the unblock: The ticket in the current way is not describing a useful user story but an implementation detail. If possible a better way would be to create a timeboxed spike solution for #109920 how to go forward, if with the approach mentioned here or the "Suggestion 2" from the parent or even a different approach.

Actions #5

Updated by okurz over 1 year ago

  • Category set to Feature requests
Actions #6

Updated by okurz over 1 year ago

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

Discussed in the estimation meeting 2023-04-27 and we understood #126527#note-9 in a way that we don't need this.

Actions #7

Updated by okurz over 1 year ago

  • Parent task changed from #109920 to #94105
Actions

Also available in: Atom PDF