openqa-label-known-issues: Remove obsolete handling of poo#61922 #93
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We encountered many jobs that have poo#61922 as label from openqa-label-known-issues. This comes from openqa-label-known-issues that directly detects openQA jobs without any logs and marks as such. In the meantime we have the "reason" field which in the case of the mentioned jobs says something along the lines of "abandoned: associated worker $host:instance re-connected but abandoned the job" and likely the job was automatically retriggered at that time by openQA itself so we should not need to handle the issue anymore in openqa-label-known-issues explicitly. Related progress issue: https://progress.opensuse.org/issues/96019
Martchus
approved these changes
Jul 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We encountered many jobs that have poo#61922 as label from
openqa-label-known-issues. This comes from openqa-label-known-issues that
directly detects openQA jobs without any logs and marks as such. In the
meantime we have the "reason" field which in the case of the mentioned jobs
says something along the lines of "abandoned: associated worker $host:instance
re-connected but abandoned the job" and likely the job was automatically
retriggered at that time by openQA itself so we should not need to handle the
issue anymore in openqa-label-known-issues explicitly.
Related progress issue: https://progress.opensuse.org/issues/96019