Skip to content

[DO NOT MERGE] start building Enzyme in CI #140064

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

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

ZuseZ4
Copy link
Member

@ZuseZ4 ZuseZ4 commented Apr 20, 2025

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 [Ready]
140104 [Landed]
140030 [Landed]
140049 [Almost ready]
140244 [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.

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

@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Apr 20, 2025
@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 20, 2025

@bors try

@bors
Copy link
Collaborator

bors commented Apr 20, 2025

⌛ Trying commit 1302345 with merge 85630b7...

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
@rust-log-analyzer

This comment has been minimized.

@rust-log-analyzer

This comment has been minimized.

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 20, 2025

@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
@bors
Copy link
Collaborator

bors commented Apr 20, 2025

⌛ Trying commit ca4cd19 with merge 22fa494...

@rust-log-analyzer

This comment has been minimized.

@rust-timer

This comment has been minimized.

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Apr 20, 2025
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented Apr 20, 2025

💔 Test failed - checks-actions

@bors bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Apr 20, 2025
@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 21, 2025

@jieyouxu I tried running both tests/ui/feature-gates/feature-gate-autodiff-use.rs and tests/ui/autodiff/visibility.rs with llvm.enzyme being either true or false in bootstrap.toml. I couldn't reproduce it that way. I also tried to copy the --cfg flags I saw in the log. Do you have recommendations on how to reproduce it locally (so I can update my rustc dev docs)?

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 21, 2025

@bors try @rust-timer queue

@rust-timer

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
@bors
Copy link
Collaborator

bors commented Apr 21, 2025

⌛ Trying commit 4b353ac with merge e690318...

@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented Apr 21, 2025

☀️ Try build successful - checks-actions
Build commit: e690318 (e690318f2c437976796a1aff8927ff8793b4d1b7)

@rust-timer

This comment has been minimized.

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (e690318): comparison URL.

Overall result: ❌ regressions - please read the text below

Benchmarking 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 @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: -S-waiting-on-perf +perf-regression

Instruction count

This 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.

mean range count
Regressions ❌
(primary)
2.6% [2.4%, 2.8%] 4
Regressions ❌
(secondary)
1.5% [1.0%, 2.3%] 11
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.6% [2.4%, 2.8%] 4

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.

mean range count
Regressions ❌
(primary)
0.9% [0.4%, 1.8%] 27
Regressions ❌
(secondary)
3.2% [1.5%, 7.4%] 9
Improvements ✅
(primary)
-0.7% [-0.7%, -0.7%] 1
Improvements ✅
(secondary)
-1.8% [-2.1%, -1.6%] 3
All ❌✅ (primary) 0.8% [-0.7%, 1.8%] 28

Cycles

Results (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.

mean range count
Regressions ❌
(primary)
0.8% [0.4%, 2.8%] 10
Regressions ❌
(secondary)
2.3% [1.8%, 3.0%] 4
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 0.8% [0.4%, 2.8%] 10

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 775.102s -> 775.899s (0.10%)
Artifact size: 365.03 MiB -> 365.22 MiB (0.05%)

@rustbot rustbot added perf-regression Performance regression. and removed S-waiting-on-perf Status: Waiting on a perf run to be completed. labels Apr 21, 2025
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 [Ready]
139308 [Ready, blocked on 139700]
140104 [Almost ready]
140030 [Landed]
140049 [Almost ready]
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

succeeded try with plugins & llvm-enzyme enabled:  dist-x86_64-linux

failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (rust-lang#140064 (comment))

try-job: dist-aarch64-linux
@bors
Copy link
Collaborator

bors commented Apr 22, 2025

☀️ Try build successful - checks-actions
Build commit: 6a4ba31 (6a4ba3120960f17494a199fa78c9e84313eab700)

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 22, 2025

@bors try

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Trying commit a1d9041 with merge c59c2d4...

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 22, 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 [Ready]
139308 [Ready, blocked on 139700]
140104 [Almost ready]
140030 [Landed]
140049 [Almost ready]
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.

A fix for 140137 (Apple CI) would be nice, but I'm also happy to start with the working x86-64 linux as the most common target, and expand from there.

r? `@oli-obk`

Tracking:

- rust-lang#124509

succeeded try with plugins & llvm-enzyme enabled:  dist-x86_64-linux
succeeded try with plugins & llvm-enzyme enabled:  dist-aarch64-linux

failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (rust-lang#140064 (comment))

try-job: dist-x86_64-mingw
@rust-log-analyzer

This comment has been minimized.

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

💔 Test failed - checks-actions

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 22, 2025

I guess linking against LLVM doesn't work here on mingw, but I don't really want to deal with linker issues right now, so I'll postpone windows support. The more relevant MSVC builders wouldn't work due to an Enzyme bug anyway.

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 22, 2025

Now testing Enzyme only, without enabling LLVM's plugin interface, since I made it optional in a previous enzyme PR. That might save us a few bytes.
@bors try

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Trying commit 142ec6f with merge f3fdf02...

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 22, 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 [Ready]
139308 [Ready, blocked on 139700]
140104 [Almost ready]
140030 [Landed]
140049 [Almost ready]
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.

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 & llvm-enzyme enabled:  dist-x86_64-linux
succeeded try with plugins & llvm-enzyme enabled:  dist-aarch64-linux

**MacOS**
failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (rust-lang#140064 (comment))

**Windows**
failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (rust-lang#140064 (comment))

try-job: dist-x86_64-linux
try-job: dist-aarch64-linux
@ZuseZ4 ZuseZ4 changed the title [DO NOT MERGE] start building enzyme on x86_64-gnu-llvm-{19|20} builders [DO NOT MERGE] start building Enzyme in CI Apr 22, 2025
@bors
Copy link
Collaborator

bors commented Apr 22, 2025

☀️ Try build successful - checks-actions
Build commit: f3fdf02 (f3fdf02e223bd9e86773eadbec66390c66860efa)

@Kobzol
Copy link
Contributor

Kobzol commented Apr 22, 2025

@bors try

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 22, 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 [Ready]
139308 [Ready, blocked on 139700]
140104 [In the queue]
140030 [Landed]
140049 [Almost ready]
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.

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 & llvm-enzyme enabled:  dist-x86_64-linux
succeeded try with plugins & llvm-enzyme enabled:  dist-aarch64-linux

**MacOS**
failed try with plugins & llvm-enzyme enabled: dist-x86_64-apple (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (rust-lang#140064 (comment))

**Windows**
failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (rust-lang#140064 (comment))

try-job: dist-x86_64-linux
try-job: dist-aarch64-linux
@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Trying commit 142ec6f with merge 2400b35...

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 22, 2025

@Kobzol out of curiosity, what's the reason to run the same try build twice, do you expect some caching?

@Kobzol
Copy link
Contributor

Kobzol commented Apr 22, 2025

Yes, the build took an hour longer than normally, if it is so long even with caching, then we need to do something about that :) But the bootstrap timings seemed to be similar, so I expect that only the Docker cache was busted, hopefully with caching it will be faster now.

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

☀️ Try build successful - checks-actions
Build commit: 2400b35 (2400b35a4705e2b34122a4c8d7c72bde4920f6ab)

@Kobzol
Copy link
Contributor

Kobzol commented Apr 22, 2025

Cached duration looks fine.

@ZuseZ4
Copy link
Member Author

ZuseZ4 commented Apr 22, 2025

@bors try
(now without llvm's plugin interface, less things might fail)

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

⌛ Trying commit 4a9fab7 with merge 1af1719...

bors added a commit to rust-lang-ci/rust that referenced this pull request Apr 22, 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 [In the queue]
139308 [Ready, blocked on 139700]
140104 [In the queue]
140030 [Landed]
140049 [Almost ready]
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.

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 (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-apple-various (rust-lang#140064 (comment))
failed try with plugins & llvm-enzyme enabled: dist-aarch64-apple (rust-lang#140064 (comment))

**Windows**
failed try with plugins & llvm-enzyme enabled: dist-x86_64-mingw (rust-lang#140064 (comment))

try-job: dist-aarch64-apple
@rust-log-analyzer
Copy link
Collaborator

The job dist-aarch64-apple failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)
Updating files:  98% (51863/52921)
Updating files:  99% (52392/52921)
Updating files: 100% (52921/52921)
Updating files: 100% (52921/52921), done.
Switched to a new branch 'try'
branch 'try' set up to track 'origin/try'.
##[endgroup]
[command]/opt/homebrew/bin/git log -1 --format=%H
1af17195170f0299e2e411f296584a96ce64447a
##[group]Run src/ci/scripts/setup-environment.sh
src/ci/scripts/setup-environment.sh
---
file:.git/config remote.origin.url=https://github.com/rust-lang-ci/rust
file:.git/config remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
file:.git/config gc.auto=0
file:.git/config http.https://github.com/.extraheader=AUTHORIZATION: basic ***
file:.git/config branch.try.remote=origin
file:.git/config branch.try.merge=refs/heads/try
file:.git/config remote.upstream.url=https://github.com/rust-lang/rust
file:.git/config remote.upstream.fetch=+refs/heads/*:refs/remotes/upstream/*
file:.git/config submodule.library/backtrace.active=true
file:.git/config submodule.library/backtrace.url=https://github.com/rust-lang/backtrace-rs.git
file:.git/config submodule.library/stdarch.active=true
---
CMAKE_aarch64-apple-darwin = None
CMAKE_aarch64_apple_darwin = None
HOST_CMAKE = None
CMAKE = None
running: cd "/Users/runner/work/rust/rust/build/aarch64-apple-darwin/enzyme/build" && CMAKE_PREFIX_PATH="" DESTDIR="" LC_ALL="C" LLVM_CONFIG_REAL="/Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm/bin/llvm-config" "cmake" "/Users/runner/work/rust/rust/src/tools/enzyme/enzyme/" "-DCMAKE_OSX_ARCHITECTURES=arm64" "-DCMAKE_INSTALL_MESSAGE=LAZY" "-DCMAKE_C_COMPILER_LAUNCHER=sccache" "-DCMAKE_CXX_COMPILER_LAUNCHER=sccache" "-DCMAKE_C_COMPILER=/Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" "-DCMAKE_CXX_COMPILER=/Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++" "-DCMAKE_ASM_COMPILER=/Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang" "-DCMAKE_C_FLAGS=-ffunction-sections -fdata-sections -fPIC --target=arm64-apple-macosx -mmacosx-version-min=11 -isysroot /Applications/Xcode_15.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk -fdebug-prefix-map=/Users/runner/work/rust/rust=/rustc/llvm" "-DCMAKE_CXX_FLAGS=-ffunction-sections -fdata-sections -fPIC --target=arm64-apple-macosx -mmacosx-version-min=11 -isysroot /Applications/Xcode_15.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk -stdlib=libc++ -fdebug-prefix-map=/Users/runner/work/rust/rust=/rustc/llvm" "-DCMAKE_SHARED_LINKER_FLAGS= -static-libstdc++" "-DCMAKE_MODULE_LINKER_FLAGS= -static-libstdc++" "-DCMAKE_EXE_LINKER_FLAGS= -static-libstdc++" "-DLLVM_ENABLE_ASSERTIONS=ON" "-DENZYME_EXTERNAL_SHARED_LIB=ON" "-DLLVM_DIR=/Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm" "-DCMAKE_INSTALL_PREFIX=/Users/runner/work/rust/rust/build/aarch64-apple-darwin/enzyme" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC --target=arm64-apple-macosx -mmacosx-version-min=11 -isysroot /Applications/Xcode_15.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk" "-DCMAKE_BUILD_TYPE=Release"
-- The C compiler identification is AppleClang 15.0.0.15000309
-- The CXX compiler identification is AppleClang 15.0.0.15000309
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Applications/Xcode_15.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
LLVM_SHLIBEXT=.dylib
LLVM ABS DIR /Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm/lib/cmake/llvm
CMAKE_PREFIX_PATH 
-- Found ZLIB: /Applications/Xcode_15.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.5.sdk/usr/lib/libz.tbd (found version "1.2.12")
LLVM_ENABLE_PLUGINS OFF
Setting ENZYME_ENABLE_PLUGINS OFF
found llvm match  dir /Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm/lib/cmake/llvm
---
mlir dir 
found Clang 0
found MLIR 0
LLVM_INSTALL_PREFIX: /Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm
LLVM_INCLUDE_DIRS: /Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm/include
found LLVM definitions -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
found LLVM version 20
first llvm include directory/Users/runner/work/rust/rust/build/aarch64-apple-darwin/llvm/include
-- Looking for mpfr.h
-- Looking for mpfr.h - not found
MPFR lib: /opt/homebrew/lib/libmpfr.dylib

@bors
Copy link
Collaborator

bors commented Apr 22, 2025

💔 Test failed - checks-actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants