Project

General

Profile

action #124370

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

Added by ph03nix 4 months ago. Updated 4 months ago.

Status:
Blocked
Priority:
Normal
Assignee:
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

Blocked by openQA Project - action #122296: Fix openqa-trigger-bisect-jobs to actually remove incidents from bisection tests againNew2022-12-21

History

#1 Updated by okurz 4 months ago

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

#2 Updated by okurz 4 months ago

  • Category set to Concrete Bugs
  • Status changed from New to Blocked
  • Assignee set to szarate

#3 Updated by okurz 4 months ago

  • Project changed from openQA Project to openQA Tests
  • 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 Concrete Bugs to Bugs in existing tests

Also available in: Atom PDF