Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge #4500 to the chrome branch #4501

Merged
merged 1 commit into from
Dec 13, 2024
Merged

Merge #4500 to the chrome branch #4501

merged 1 commit into from
Dec 13, 2024

Conversation

vitorguidi
Copy link
Collaborator

Merging #4500 into the chrome branch, doing CI checks first

…COUNT (#4500)

### Motivation

The UNTRIAGED_TESTCASE_COUNT metric worked as expected, however it is
hard to figure out which job the testcase belongs to, and why the
testcase is stuck. This PR adds the job label, and a status one, which
can be one of four values:

PENDING_CRITICAL_TASKS = 'pending_critical_tasks'
PENDING_PROGRESSION = 'pending_progression'
PENDING_GROUPING = 'pending_grouping'
PENDING_FILING = 'pending_filing'

Since (job, status) tuples might disappear from one triage run to the
next, the period of time the gauge is valid for should be, at most, the
interval at which the triage cronjob runs, otherwise it might overcount
things.

Part of #4271
@vitorguidi vitorguidi changed the title Merge Merge 4501 to the chrome branch Dec 13, 2024
@vitorguidi vitorguidi changed the title Merge 4501 to the chrome branch Merge 4500 to the chrome branch Dec 13, 2024
@vitorguidi vitorguidi changed the title Merge 4500 to the chrome branch Merge #4500 to the chrome branch Dec 13, 2024
@vitorguidi vitorguidi merged commit fc61aff into chrome Dec 13, 2024
3 checks passed
@vitorguidi vitorguidi deleted the chore/merge-yet-again branch December 13, 2024 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant