-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[export] enable custom tag metadata re-export test #136048
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
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/136048
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 17adc5f with merge base 3406ac2 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
b507694 to
a4b725b
Compare
d53da39 to
fd0b1e0
Compare
|
@yiming0416 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
fd0b1e0 to
5e460dd
Compare
|
@yiming0416 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
5e460dd to
7550a6c
Compare
|
@yiming0416 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: Improves and enables a commented out test originally introduced in #131912 In `test_custom_tag_metadata_re_export()`, we check the added "custom" metadata to given nodes is preserved and not copied to other nodes after re-exporting Reviewed By: zhxchen17 Differential Revision: D62880574 Pulled By: yiming0416
7550a6c to
17adc5f
Compare
|
This pull request was exported from Phabricator. Differential Revision: D62880574 |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@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) |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
|
@pytorchbot merge -f "landed internally" |
|
The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command |
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 |
Improves and enables a commented out test originally introduced in pytorch#131912 In `test_custom_tag_metadata_re_export()`, we check the added "custom" metadata to given nodes is preserved and not copied to other nodes after re-exporting Pull Request resolved: pytorch#136048 Approved by: https://github.com/zhxchen17
Improves and enables a commented out test originally introduced in #131912
In
test_custom_tag_metadata_re_export(), we check the added "custom" metadata to given nodes is preserved and not copied to other nodes after re-exporting