about summary refs log tree commit diff
path: root/src/ci/docker/scripts/rfl-build.sh
AgeCommit message (Collapse)AuthorLines
2025-09-09CI: rfl: move job forward to Linux v6.17-rc5 to remove temporary commitsMiguel Ojeda-3/+1
v6.17-rc5 contains the equivalent of the two commits we had here, thus move the Rust for Linux job forward to that so that we don't need the temporary commits anymore. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-09-03CI: rfl: move job forward to Linux v6.17-rc3 plus 2 commitsMiguel Ojeda-1/+2
This upgrades the Rust CI from v6.16-rc1 plus a temporary commit for the >= 1.91 target spec [1] to v6.17-rc3 with two commits pending to be merged upstream -- one for the same target spec format change [1] and another for the `file_as_c_str` change [2]. Link: https://github.com/rust-lang/rust/pull/144443 [1] Link: https://github.com/rust-lang/rust/pull/145928 [2] Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-08-27CI: rfl: support Rust >= 1.91.0 target specMiguel Ojeda-1/+2
To unblock the Rust CI in PR [1], use a temporary commit from Rust for Linux that supports the future target spec format. Link: https://github.com/rust-lang/rust/pull/144443 [1] Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-06-23Remove `build --stage 0` from CI scriptsJakub Beránek-1/+1
2025-06-08CI: rfl: move job forward to Linux v6.16-rc1Miguel Ojeda-2/+1
Remove the comment on top as well, since that issue is now fixed in this new tag. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-05-23Remove #![feature(let_chains)] from libcoreest31-1/+2
2025-04-29CI: rfl: move job forward to Linux v6.15-rc4Miguel Ojeda-1/+1
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-03-03Do not use rustup to build Rust for LinuxJakub Beránek-10/+8
2025-02-17CI: rfl: move job forward to Linux v6.14-rc3Miguel Ojeda-2/+2
Linux v6.14-rc3 contains commit 6273a058383e ("x86: rust: set rustc-abi=x86-softfloat on rustc>=1.86.0"), which resolves the error from https://github.com/rust-lang/rust/pull/136146. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2025-02-03patch RfL jobRalf Jung-2/+2
2024-12-03CI: rfl: move job forward to Linux v6.13-rc1Miguel Ojeda-2/+2
Linux v6.13-rc1 contains commit 28e848386b92 ("rust: block: fix formatting of `kernel::block::mq::request` module"), which in turn contains commit c95bbb59a9b2 ("rust: enable arbitrary_self_types and remove `Receiver`"), which is why we had a hash rather than a tag. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-10-23CI: rfl: use rust-next temporary commitAdrian Taylor-1/+1
Commit c95bbb59a9b22f9b838b15d28319185c1c884329 within rust-next contains some changes required to be compatible with upcoming arbitraty self types work. Roll RFL CI forward to the latest rust-next to include that work. Related: https://github.com/rust-lang/rust/pull/130225 https://github.com/rust-lang/rust/issues/44874
2024-10-07CI: rfl: move job forward to Linux v6.12-rc2Miguel Ojeda-1/+1
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: factor out build targetsMiguel Ojeda-8/+9
It will make it easier to add more in the future. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add macro expanded source build (`-Zunpretty=expanded`)Miguel Ojeda-0/+8
This particular target does not expand into much code, so it is a good first candidate to see if we could keep this in the CI. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a `rustfmt` runMiguel Ojeda-2/+9
This change will also remove the current warnings in the build due to `rustfmt` not being available (for `bindgen` output): error: 'rustfmt' is not installed for the custom toolchain 'local'. note: this is a custom toolchain, which cannot use `rustup component add` help: if you built this toolchain from source, and used `rustup toolchain link`, then you may be able to build the component with `x.py` Failed to run rustfmt: Internal rustfmt error (non-fatal, continuing) Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a Clippy buildMiguel Ojeda-2/+13
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: switch to a stage 2 buildMiguel Ojeda-2/+2
Apparently tools like `rustfmt` require it in order to find the right `librustc_driver.so` without extra tweaks. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-28CI: rfl: add a couple comments to split the steps and document themMiguel Ojeda-0/+9
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-08-23CI: rfl: move to temporary commitMiguel Ojeda-2/+2
Link: https://github.com/rust-lang/rust/pull/129416 Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-07-29CI: rfl: build the documentationMiguel Ojeda-0/+3
Since the `rfl` CI job has not had almost any issue for some weeks, it is a good time to try to increase a bit the scope of what it tests. The kernel does not use any particular `rustdoc` unstable issue (apart from the doctests ones) so far, so in principle it should not introduce extra issues here, and may be a good extra test case for Rust. In addition, it may help to test new unstable features in the future. In the worst case, we can revert it. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-07-29CI: rfl: build the generated doctestsMiguel Ojeda-1/+2
We were already generating the doctests, which should already catch most issues with our hack around `--test-builder` and `--no-run`. However, we were not building the result of that transformation, thus build it for completeness and to ensure the hack may not have produced something completely broken. In the worst case, we can revert it. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-07-29CI: move RFL job forward to v6.11-rc1Miguel Ojeda-1/+1
The tag has been released today, and since the original hash we had in the Rust CI (which was ~v6.10-rc1), we have accumulated a fair amount of changes and new code. In particular, v6.11-rc1 is the first Linux tag where the kernel is supporting an actual minimum Rust version (1.78.0), rather than a single version. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-06-10CI: add Rust for Linux `auto` jobJakub Beránek-0/+68