[Split Build] Test split build in CI #126699
Open
+47
−53
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/126699
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New Failures, 2 Unrelated FailuresAs of commit 92898c4 with merge base 304c934 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Open
PaliC
removed
the
keep-going
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
Specifically this PR tests building the split build on our manywheel builds on trunk Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing. [ghstack-poisoned]
|
Rebased |
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.
Stack from ghstack (oldest at bottom):
Specifically this PR tests building the split build on our manywheel builds on trunk
Also until we come up with a better name "libtorch" was renamed to "libtorchsplit" so we don't accidentally download the pip package which screws up testing.