diff options
| author | Samuel Tardieu <sam@rfc1149.net> | 2025-08-02 11:24:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-08-02 11:24:23 +0200 |
| commit | cafd9fb2d3f2b5179308f3c736341fa9cec61867 (patch) | |
| tree | 166cc7d5bf95456f903e02d6888f8b3e791bd35c /compiler/rustc_hir/src | |
| parent | ce1961bbfcc71818484d340ea4924f28417657e8 (diff) | |
| parent | 8b90847416d5678d784942b46c05f8c97caef83d (diff) | |
| download | rust-cafd9fb2d3f2b5179308f3c736341fa9cec61867.tar.gz rust-cafd9fb2d3f2b5179308f3c736341fa9cec61867.zip | |
Rollup merge of #144395 - folkertdev:fortanix-run-make-test, r=jieyouxu
update fortanix tests Firstly, as far as I can tell, no CI job actually runs any of the fortanix tests? Maybe I'm missing the job that runs these tests though? In any case, the `assembly` tests now use `minicore`, meaning that they will run regardless of the host architecture (specifically, they will run during a standard PR CI build). The run-make test is actually broken, and I'd propose to make it just `cargo build` rather than `cargo run`. We can have a separate test for actually running the program, if desired. Also this test is subject to https://github.com/rust-lang/rust/issues/128733, so I'd like to re-evaluate what parts of the C/C++ compilation are actually required or useful. cc [``@jethrogb](https://github.com/jethrogb)`` [``@raoulstrackx](https://github.com/raoulstrackx)`` [``@aditijannu](https://github.com/aditijannu)`` r? ``@jieyouxu``
Diffstat (limited to 'compiler/rustc_hir/src')
0 files changed, 0 insertions, 0 deletions