Script to generate NJT OpInfo testing report #143311
Closed
Conversation
This file contains hidden or 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
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/143311
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New FailuresAs of commit e19054b with merge base 46390e9 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  TODO: It might be interesting to have a collapsible xfail / skip explorer? Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  ~~TODO: It might be interesting to have a collapsible xfail / skip explorer?~~ Added this Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
<
8000
pre class="color-fg-muted ws-pre-wrap">
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.
~~TODO: It might be interesting to have a collapsible xfail / skip explorer?~~ Added this
Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice.
TBD how to incorporate this into the NJT docs.
[ghstack-poisoned]
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for `(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous)`, including the (color-coded) success rate / number of xfails / number of skips.  ~~TODO: It might be interesting to have a collapsible xfail / skip explorer?~~ Added this Yes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice. TBD how to incorporate this into the NJT docs. [ghstack-poisoned]
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
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.
Stack from ghstack (oldest at bottom):
I hacked together a script to parse skips / xfails for the OpInfo-based tests and visualize the status of passing tests in a table. Results are reported op-wise for
(forward, compile_forward, backward, compile_backward) x (contiguous, non-contiguous), including the (color-coded) success rate / number of xfails / number of skips.TODO: It might be interesting to have a collapsible xfail / skip explorer?Added thisYes I know it looks terrible! I'm not a frontend dev and it's more important to visualize the data so I can prioritize fixes than spend time making it look nice.
TBD how to incorporate this into the NJT docs.