[DO NOT MERGE] start building Enzyme in CI #140064
Open
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
rustbot
added
A-testsuite
|
@bors try |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 20, 2025
[DO NOT MERGE] start building enzyme on x86_64-gnu-llvm-{19|20} builders
My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs:
rust-lang#139700
rust-lang#139308
rust-lang#139557
rust-lang#140030
rust-lang#140049
The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders.
r? `@oli-obk`
Tracking:
- rust-lang#124509
try-job: x86_64-gnu-llvm-19
try-job: x86_64-gnu-llvm-20
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@bors try @rust-timer queue |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 20, 2025
[DO NOT MERGE] start building enzyme on x86_64-gnu-llvm-{19|20} builders
My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs:
rust-lang#139700
rust-lang#139308
rust-lang#139557
rust-lang#140030
rust-lang#140049
The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders.
r? `@oli-obk`
Tracking:
- rust-lang#124509
try-job: dist-x86_64-linux
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rustbot
added
the
S-waiting-on-perf
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
bors
added
S-waiting-on-author
|
@jieyouxu I tried running both |
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Apr 21, 2025
[DO NOT MERGE] start building enzyme on x86_64-gnu-llvm-{19|20} builders
My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR):
139700
139308
139557
140030
140049
The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders.
r? `@oli-obk`
Tracking:
- rust-lang#124509
try-job: dist-x86_64-linux
This comment has been minimized.
This comment has been minimized.
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (e690318): comparison URL. Overall result: ❌ regressions - please read the text belowBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary 0.8%, secondary 1.9%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (primary 0.8%, secondary 2.3%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 775.102s -> 775.899s (0.10%) |
rustbot
added
perf-regression
This comment has been minimized.
This comment has been minimized.
|
@bors try |
bors
added a commit
that referenced
this pull request
May 26, 2025
[DO NOT MERGE] start building Enzyme in CI My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR): 139700 [Landed] 139308 [Landed] 140104 [Landed] 140030 [Landed] 140049 [Almost ready] 140244 [Closed due to design changes] 140697[WIP] The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders. There are some related CMake PRs which I also made in the Enzyme repo. I can temporarily merge them into the r-l/Enzyme fork, so we are not blocked on them. A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working linux (x86-64 + aarch) as the most common target, and expand from there. r? `@oli-obk` Tracking: - 124509 **Linux** succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-x86_64-linux succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-aarch64-linux **MacOS** failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-apple-various (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (#140064 (comment)) **Windows** failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (#140064 (comment)) try-job: dist-aarch64-apple
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
|
@bors try |
bors
added a commit
that referenced
this pull request
May 27, 2025
[DO NOT MERGE] start building Enzyme in CI My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR): 139700 [Landed] 139308 [Landed] 140104 [Landed] 140030 [Landed] 140049 [Almost ready] 140244 [Closed due to design changes] 140697[WIP] The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders. There are some related CMake PRs which I also made in the Enzyme repo. I can temporarily merge them into the r-l/Enzyme fork, so we are not blocked on them. A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working linux (x86-64 + aarch) as the most common target, and expand from there. r? `@oli-obk` Tracking: - 124509 **Linux** succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-x86_64-linux succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-aarch64-linux **MacOS** failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-apple-various (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (#140064 (comment)) **Windows** failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (#140064 (comment)) try-job: dist-aarch64-apple
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
@bors try |
bors
added a commit
that referenced
this pull request
May 27, 2025
[DO NOT MERGE] start building Enzyme in CI My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR): 139700 [Landed] 139308 [Landed] 140104 [Landed] 140030 [Landed] 140049 [Almost ready] 140244 [Closed due to design changes] 140697[WIP] The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders. There are some related CMake PRs which I also made in the Enzyme repo. I can temporarily merge them into the r-l/Enzyme fork, so we are not blocked on them. A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working linux (x86-64 + aarch) as the most common target, and expand from there. r? `@oli-obk` Tracking: - 124509 **Linux** succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-x86_64-linux succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-aarch64-linux **MacOS** failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-apple-various (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (#140064 (comment)) **Windows** failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (#140064 (comment)) try-job: dist-aarch64-apple
This comment has been minimized.
This comment has been minimized.
|
💔 Test failed - checks-actions |
|
@bors try |
bors
added a commit
that referenced
this pull request
May 27, 2025
[DO NOT MERGE] start building Enzyme in CI My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR): 139700 [Landed] 139308 [Landed] 140104 [Landed] 140030 [Landed] 140049 [Almost ready] 140244 [Closed due to design changes] 140697[WIP] The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders. There are some related CMake PRs which I also made in the Enzyme repo. I can temporarily merge them into the r-l/Enzyme fork, so we are not blocked on them. A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working linux (x86-64 + aarch) as the most common target, and expand from there. r? `@oli-obk` Tracking: - 124509 **Linux** succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-x86_64-linux succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-aarch64-linux **MacOS** failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-apple-various (#140064 (comment)) failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (#140064 (comment)) **Windows** failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (#140064 (comment)) try-job: dist-aarch64-apple
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
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.
My goal is to put this in CI on April 26, to have a week to land some of the outstanding PRs (removed # in front of it to avoid spamming them every time I do a try build in this PR):
139700 [Landed]
139308 [Landed]
140104 [Landed]
140030 [Landed]
140049 [Landed]
140244 [Closed due to design changes]
140697[In the queue]
The autodiff flags PR should land first, but otherwise they don't overlap and are mostly ready, so it shouldn't be too hard to land them. In the meantime, I'll experiment here with some builders. There are some related CMake PRs which I also made in the Enzyme repo. I can temporarily merge them into the r-l/Enzyme fork, so we are not blocked on them.
A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working linux (x86-64 + aarch) as the most common target, and expand from there.
r? @oli-obk
Tracking:
Linux
succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-x86_64-linux
succeeded try with plugins and without plugins & with llvm-enzyme enabled: dist-aarch64-linux
MacOS
failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (#140064 (comment))
Windows
failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (#140064 (comment))
try-job: dist-aarch64-apple