[ci] Ignore JUnit upload failures #13142
Merged
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
These are never really signal-carrying so there's no need for it to show up as red on CI jobs. This also adds retries to the `git checkout` step within Jenkins to deal with GitHub instability.
Collaborator
|
Thanks for contributing to TVM! Please refer to the contributing guidelines https://tvm.apache.org/docs/contribute/ for useful information and tips. Please request code reviews from Reviewers by @-ing them in a comment.
Generated by tvm-bot |
driazati
added a commit
that referenced
this pull request
Oct 19, 2022
masahi
approved these changes
Oct 21, 2022
janetsc
pushed a commit
to janetsc/tvm
that referenced
this pull request
Oct 21, 2022
These are never really signal-carrying so there's no need for it to show up as red on CI jobs. This also adds retries to the `git checkout` step within Jenkins to deal with GitHub instability. Co-authored-by: driazati <driazati@users.noreply.github.com>
xinetzone
pushed a commit
to daobook/tvm
that referenced
this pull request
Nov 10, 2022
These are never really signal-carrying so there's no need for it to show up as red on CI jobs. This also adds retries to the `git checkout` step within Jenkins to deal with GitHub instability. Co-authored-by: driazati <driazati@users.noreply.github.com>
xinetzone
pushed a commit
to daobook/tvm
that referenced
this pull request
Nov 25, 2022
These are never really signal-carrying so there's no need for it to show up as red on CI jobs. This also adds retries to the `git checkout` step within Jenkins to deal with GitHub instability. Co-authored-by: driazati <driazati@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These are never really signal-carrying so there's no need for it to show
up as red on CI jobs. This also adds retries to the
git checkoutstepwithin Jenkins to deal with GitHub instability. This should help avoid
confusing situations like in #13136