Use CHERIoT-Platform's LLVM + CI to check it #2
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
xdoardo
force-pushed
the
cheri-ci
branch
30 times, most recently
from
6f4e2d3 to
aab3649
Compare
xdoardo
force-pushed
the
cheri-ci
branch
6 times, most recently
from
6375f63 to
c707d83
Compare
xdoardo
changed the title
xdoardo
force-pushed
the
cheri-ci
branch
10 times, most recently
from
57e7b90 to
1384154
Compare
|
Alright, CI is now trying to run |
resistor
reviewed
Aug 25, 2025
.cirrus.yml
Outdated
| - export CCACHE_REMOTE_STORAGE="http://${CIRRUS_HTTP_CACHE_HOST}/${CIRRUS_OS}/" | ||
| - export CCACHE_REMOTE_ONLY=1 | ||
| - env | ||
| test_script: CC="clang" CXX="clang" ./x check |
seharris
approved these changes
Aug 26, 2025
|
Currently it uses Cirrus CI, which is already used in the llvm-project repo. |
xdoardo
pushed a commit
to xdoardo/cheri-rust
that referenced
this pull request
Sep 1, 2025
Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [CHERIoT-Platform#1 of Batch CHERIoT-Platform#2] Part of rust-lang/rust#133895 Methodology: 1. Refer to the previously written `tests/ui/SUMMARY.md` 2. Find an appropriate category for the test, using the original issue thread and the test contents. 3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers) 4. Rename the tests to make their purpose clearer Inspired by the methodology that `@Kivooeo` was using. r? `@jieyouxu`
xdoardo
pushed a commit
to xdoardo/cheri-rust
that referenced
this pull request
Sep 1, 2025
Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [CHERIoT-Platform#2 of Batch CHERIoT-Platform#2] Part of rust-lang/rust#133895 Methodology: 1. Refer to the previously written `tests/ui/SUMMARY.md` 2. Find an appropriate category for the test, using the original issue thread and the test contents. 3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers) 4. Rename the tests to make their purpose clearer Inspired by the methodology that `@Kivooeo` was using. r? `@jieyouxu`
xdoardo
pushed a commit
that referenced
this pull request
Sep 29, 2025
Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#3 of Batch #2] Part of rust-lang/rust#133895 Methodology: 1. Refer to the previously written `tests/ui/SUMMARY.md` 2. Find an appropriate category for the test, using the original issue thread and the test contents. 3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers) 4. Rename the tests to make their purpose clearer Inspired by the methodology that `@Kivooeo` was using. r? `@jieyouxu`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I think I disabled the CI tasks from rust-lang/rust. I want to check if it is true.
I might use this PR to do some tests: I'd like to see if we can have a simple CI job that does sanity checks, such as running
tidyand compilingrustcon a selection of target machines using CHERIoT-Platform's LLVM.Edit: this is done by changing the default remote and branch of the llvm-project submodule in Rust to the ones from CHERIoT-platform, which might be a debatable choice. Also, notice that this commit only sets up the submodule and adds sanity checks in CI, but does not change the Rust/C++ code in rustc that re-exports and links to the LLVM API: CI is therefore bound to fail for now :)