build-configs.yaml: move rust-next to Rust 1.68
#1926
Conversation
This moves both `rust-for-linux_rust-next` and `next`'s Rust variant. As discussed [1], for this kind of upgrades, we will move KernelCI first and then I will apply push the branch. The run is expected to fail if it happens to run between those two moves. Link: kernelci#1890 (comment) [1] Signed-off-by: Miguel Ojeda <[email protected]>
|
This is now going to be deployed on staging.kernelci.org and it should be tested with a full linux-next build this weekend. As long as this produces meaningful results it should land in production next week. |
|
Thanks Guillaume! Will similar updates (i.e. upgrades to the Rust compiler) take about a week to land, usually? (i.e. asking so that I can schedule/plan the PRs accordingly) |
|
Production updates for linux.kernelci.org typically happen every Monday, so yes by default it should take at most a week. If you need to fast-track something that's always possible with some more manual intervention. In the meantime there should be some results on staging by tomorrow here: Today's build was with |
|
Sounds good, thanks a lot! |
|
There's an issue, the Docker image is missing for the staging builds: Taking a look, I think a new repository should be added in Docker Hub. The kernel build with rustc-1.68 can be rerun once that's fixed so I'll post an update later. |
|
OK the image being built didn't have the |
|
Results are in: @ojeda There are build errors but I guess that's expected based on previous discussions. Please confirm this is OK and we can merge the PR. |
|
The build log looks fine to me, thanks! I would expect perhaps some of the lines from |
|
More results from the full linux-next build on staging from this weekend: |
This moves both
rust-for-linux_rust-nextandnext's Rust variant.As discussed [1], for this kind of upgrades, we will move KernelCI first and then I will apply push the branch. The run is expected to fail if it happens to run between those two moves.
Link: #1890 (comment) [1]