[CI] Do not run check-in-tree after pushes to llvm_release_* #2793
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
The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests.
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
to svenvh/SPIRV-LLVM-Translator
that referenced
this pull request
Oct 24, 2024
…elease_* (KhronosGroup#2793) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2798) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2799) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2800) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2801) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2802) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
svenvh
added a commit
that referenced
this pull request
Oct 24, 2024
…elease_* (#2793) (#2803) The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time. Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests. (cherry picked from commit 196bbc9)
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.
The check-in-tree tests take about 50 minutes to run compared to <5 minutes for check-out-of-tree. This causes considerable congestion on the runners when backports get merged to several llvm_release_* branches around the same time.
Since the value of these post-push checks is relatively low, disable them; they will still run on pull requests.