-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
NOMRG Current CI status #5009
Closed
NicolasHug
wants to merge
58
commits into
pytorch:main
from
NicolasHug:please_dont_modify_this_branch_unless_you_are_just_merging_with_main
Closed
NOMRG Current CI status #5009
NicolasHug
wants to merge
58
commits into
pytorch:main
from
NicolasHug:please_dont_modify_this_branch_unless_you_are_just_merging_with_main
Conversation
This file contains 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
💊 CI failures summary and remediationsAs of commit 84159cd (more details on the Dr. CI page):
1 failure not recognized by patterns:
🚧 4 ongoing upstream failures:These were probably caused by upstream breakages that are not fixed yet.
This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
Closed
…e_just_merging_with_main
This was referenced Jun 22, 2022
…ify_this_branch_unless_you_are_just_merging_with_main
NicolasHug
force-pushed
the
please_dont_modify_this_branch_unless_you_are_just_merging_with_main
branch
from
January 9, 2023 10:26
4b8c4c4
to
a76d1c2
Compare
…ify_this_branch_unless_you_are_just_merging_with_main
…ify_this_branch_unless_you_are_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…ify_this_branch_unless_you_are_just_merging_with_main
…ing_with_main' of github.com:NicolasHug/vision into please_dont_modify_this_branch_unless_you_are_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
…e_just_merging_with_main
I'm closing this one and opening #7990 as a replacement so we can have the pytorch bot post at the top, instead of burried in the middle of the page (GH started collapsing the comment which made it hard to access). |
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.
This is just a dummy PR to see which jobs are green and which aren't
(Useful to decide whether failures are related for newly-created PRs)
Feel free to merge with
main
every now and then to keep it up to datePlease avoid commenting about new failures below. If there are failures, it's best to open a new issue and reference this PR in the issue. Also please do not push fixes to this branch, open a new PR instead.
(same as #3808, but reopening because #3808 (comment))