-
Notifications
You must be signed in to change notification settings - Fork 25.6k
print stderr for ghstack rebase #87795
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/87795
Note: Links to docs will display an error until the docs builds have been completed. ✅ No Failures, 1 PendingAs of commit 2fecb64: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Btw the rebase job https://github.com/pytorch/pytorch/actions/runs/3325977949/jobs/5499220794 was green, so python3 .github/scripts/tryrebase.py
must have finish successfully with exit 0. I wonder if the script shallow the error somehow. I mean the raise Exception(f"\n```{push_result}```")
one line 73. Or it might not be the case here, but let's find out
it shows up as green b/c the exception is caught and a comment is posted using the exception |
@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 |
current output tends to be empty on failure, which makes it hard to debug Pull Request resolved: pytorch#87795 Approved by: https://github.com/huydhn, https://github.com/ZainRizvi
current output tends to be empty on failure, which makes it hard to debug Pull Request resolved: pytorch#87795 Approved by: https://github.com/huydhn, https://github.com/ZainRizvi
current output tends to be empty on failure, which makes it hard to debug