-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Fix Jenkins skip for CPU/GPU #9549
Merged
Merged
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
areusch
approved these changes
Nov 22, 2021
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.
thanks @driazati !
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead.
driazati
force-pushed
the
fix_docs_skip
branch
from
November 23, 2021 05:45
2b25ef4
to
22c00b5
Compare
dchauhan-arm
pushed a commit
to dchauhan-arm/tvm
that referenced
this pull request
Nov 29, 2021
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
mehrdadh
pushed a commit
to mehrdadh/tvm
that referenced
this pull request
Dec 1, 2021
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
mehrdadh
pushed a commit
to mehrdadh/tvm
that referenced
this pull request
Dec 1, 2021
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
ylc
pushed a commit
to ylc/tvm
that referenced
this pull request
Jan 7, 2022
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
yangulei
pushed a commit
to yangulei/tvm
that referenced
this pull request
Jan 11, 2022
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
ylc
pushed a commit
to ylc/tvm
that referenced
this pull request
Jan 13, 2022
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead. Co-authored-by: driazati <[email protected]>
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.
Each step should be checking the docs-only build and marking itself as skipped if necessary, these two were skipping the i386 step instead.
Thanks for contributing to TVM! Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
@areusch