Repository navigation
Only test Julia 1.10 and 1.13 on pull requests in CI - #936
Merged
Merged
Conversation
Julia 1.11, 1.12 and nightly took about 55% of the GPU agent time on pull requests over the last weeks, and on GitHub Actions most of the 8.4 runner-hours a pull request push costs, while only failing on their own once (an allocation count in a POCL test). Test them on branch builds instead, like CUDA.jl does. Pull requests also only use the slow Intel macOS runners for 1.13, and only test KernelInterface standalone on Linux, since KernelAbstractions' own tests already run its testsuite everywhere. On Buildkite, `[only julia]` or naming a back end still selects the intermediate releases on a pull request.
The push trigger listed `master` and `release-` (without wildcard), which match no branch here, so formatting was only checked on pull requests.
Contributor
Benchmark resultsCompared with d2ada37c6, the latest measured ancestor of the merge base (1 commit before it). Times are the minimum time of every benchmark. A change is unusual when it exceeds both three times the benchmark's typical change between consecutive runs on the default branch and a minimum per category (performance 3%, latency 5%, applications 3%, other 3%). A benchmark that starts or stops allocating is listed however few the allocations. A single run can still be a fluke, so rerun before drawing conclusions.
No unusual changes. All benchmarks
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #936 +/- ##
==========================================
- Coverage 82.87% 82.47% -0.41%
==========================================
Files 31 31
Lines 2564 2522 -42
==========================================
- Hits 2125 2080 -45
- Misses 439 442 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Every pull request push runs 20 GPU jobs on Buildkite (5 back ends × Julia 1.10–1.13) and 40 jobs on GitHub Actions (5 platforms × 5 Julia versions for KernelAbstractions, 3 × 5 for KernelInterface). This PR trims that down, like CUDA.jl did recently.
Over the last ~3.5 weeks:
The changes, on pull requests only:
[only julia]or the name of a back end.That cuts a pull request push to 10 GPU jobs and about 1.9 runner-hours on GitHub Actions (0.6 on macOS).
The second commit fixes the formatting check's push trigger, which listed
masterandrelease-, so it never ran on main.