Project

General

Profile

Actions
Copy link

action #124370

open

[qe-core] geekotest bisect is not removing the issue from all test repositories

Added by ph03nix almost 2 years ago. Updated 9 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-02-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

When bisecting a job group for the new test issues, the geekotest review helper script does not remove the issue in question from all *_TEST_ISSUE settings.

See e.g. https://openqa.suse.de/tests/10481564#settings - :investigate:bisect_without_27737 where 27737 should have been removed but it is still present in LTSS_TEST_ISSUES

While this should not have functional implications, it is confusing.

Impact

  • Confuses openQA reviewers

Problem

  • When bisecting jobs, the job issue number is not removed from the *_TEST_ISSUE list

Suggestion

  • Remove the bisecting job issue also from the *_TEST_ISSUE lists

Workaround

  • Try to remember that *_TEST_ISSUE is not LTSS_TEST_REPOS and therefore this has no functional implications.

Related issues 1 (1 open — 0 closed)

Blocked by openQA Project (public) - action #122296: Fix openqa-trigger-bisect-jobs to actually remove incidents from bisection tests againNewszarate2024-02-13

Actions
Actions
Copy link
 #1

Updated by okurz almost 2 years ago

  • Blocked by action #122296: Fix openqa-trigger-bisect-jobs to actually remove incidents from bisection tests again added
Actions
Copy link
 #2

Updated by okurz almost 2 years ago

  • Category set to Regressions/Crashes
  • Status changed from New to Blocked
  • Assignee set to szarate
Actions
Copy link
 #3

Updated by okurz almost 2 years ago

  • Project changed from openQA Project (public) to openQA Tests (public)
  • Subject changed from geekotest bisect is not removing the issue from all test repositories to [qe-core] geekotest bisect is not removing the issue from all test repositories
  • Category changed from Regressions/Crashes to Bugs in existing tests
Actions
Copy link
 #4

Updated by slo-gin 9 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link

Also available in: Atom PDF