-
Notifications
You must be signed in to change notification settings - Fork 2
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
update-backlog
: triage not-not PASS
ing tests
#109
Labels
Comments
Estimate: |
Expected to yield at least a dozen promoted tests. |
This was referenced May 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are quite a few tests that expect
PASS
,TIMEOUT
, andNOTRUN
outcomes (or some subset) at the test and subtest level, but notFAIL
orCRASH
outcomes. The key observation here is we haven't actually observed these to notPASS
; I'll call these "not-notPASS
ing tests". My hypothesis is that many of these will simply bePASS
ing when we run those tests in tier 2's broader timeout window. We should triage not-notPASS
ing tests with a new heuristic forupdate-backlog
.The text was updated successfully, but these errors were encountered: