[optests] Changed failures_dict format to json; automatic update of failures_dict#109110
[optests] Changed failures_dict format to json; automatic update of failures_dict#109110zou3519 wants to merge 1 commit intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/109110
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit 231ae83 with merge base a46df6e ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
18e815f to
f8bbf7a
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
f8bbf7a to
113b57b
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
113b57b to
ca76918
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
ca76918 to
9694443
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
9694443 to
0595406
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
0595406 to
9c0a3d6
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
test/minioptest_failures_dict.json
Outdated
There was a problem hiding this comment.
would be nice to do the trailing newline correctly
test/test_custom_ops.py
Outdated
There was a problem hiding this comment.
what's this helper function 🤔
There was a problem hiding this comment.
Something about internal fbcode having different codepaths to the resource :/
There was a problem hiding this comment.
type annotations would be nice
There was a problem hiding this comment.
sgtm (will probably save for a follow-up, I need to type the entire file, not just these changes)
There was a problem hiding this comment.
I guess this feels less bad when you realize this is "expect success", as opposed to "yolo it succeeded"
There was a problem hiding this comment.
My mental model is that we're talking about the status of the test:
- "skip" means we should skip the test
- "xfail" means we expect the test to fail
- "success" means we expect the test to succeed.
I could rename this "xsuccess" if we want for consistency (do you have other thoughts?) Though I'll probably land this first to avoid merge conflicts (changing "success" to something else isn't difficult, because this doesn't actually show up in the failure dict unless the user manually puts it in)
|
properly reviewed now 👍 |
|
Thanks Ed. I need to rebase this anyways because the internal tests are complaining, so, will incorporate your comments |
…ailures_dict (pytorch#109110) Summary: We changed the failures_dict format from .py to json and added a way to automatically update the failures dict (the user can set PYTORCH_OPCHECK_ACCEPT=1 to do so), assuming the tests don't crash in the process. Some details: - We introduced a FailuresDict class that handles save/load and from which one can query a test status ("xfail", "skip", etc). - PYTORCH_OPCHECK_ACCEPT=1 does not override everything. In particular: it doesn't try to update the failures dict for a test marked as "skip", but it will update it for tests marked as "xfail" or "success". - PYTORCH_OPCHECK_ACCEPT=1 also does not override the "comment" field, unless it is flipping an "xfail" into "success". - I'll update the gdoc linked in the comments with how to actually use `PYTORCH_OPCHECK_ACCEPT=1` internally (it's not trivial). Note that this isn't multithreading-safe, the current recommendation is to run the tests sequentially if the user wants to use PYTORCH_OPCHECK_ACCEPT=1. bypass-github-export-checks Test Plan: Existing tests Reviewed By: ezyang Differential Revision: D49167181
9c0a3d6 to
231ae83
Compare
|
This pull request was exported from Phabricator. Differential Revision: D49167181 |
|
@pytorchbot merge -f 'Landed internally' (Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally) |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
We changed the failures_dict format from .py to json and added a way to
automatically update the failures dict (the user can set
PYTORCH_OPCHECK_ACCEPT=1 to do so), assuming the tests don't crash in the
process.
Some details:
can query a test status ("xfail", "skip", etc).
doesn't try to update the failures dict for a test marked as "skip", but it
will update it for tests marked as "xfail" or "success".
it is flipping an "xfail" into "success".
PYTORCH_OPCHECK_ACCEPT=1 internally (it's not trivial).
Note that this isn't multithreading-safe, the current recommendation is to run
the tests sequentially if the user wants to use PYTORCH_OPCHECK_ACCEPT=1.
Differential Revision: D49167181