Skip to content

Conversation

emilio
Copy link
Contributor

@emilio emilio commented Apr 4, 2025

No description provided.

@emilio
Copy link
Contributor Author

emilio commented Apr 4, 2025

@ojeda I'm fairly sure this is a rustc regression, since the run from 3 days ago was clean... If you're aware of any known regressions in that area lmk, otherwise I can try to bisect...

@emilio
Copy link
Contributor Author

emilio commented Apr 4, 2025

Yeah, downgrading the nightly toolchain worked...

@emilio emilio added this pull request to the merge queue Apr 4, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to invalid changes in the merge commit Apr 4, 2025
@emilio emilio enabled auto-merge April 4, 2025 14:37
@emilio
Copy link
Contributor Author

emilio commented Apr 4, 2025

Now I'm very confused... I was updating the wrong toolchain, somehow the test went green, then rebased, now red again... But yeah there was a rustc (stable) release yesterday so that probably explains the breakage at least...

 * Downgrade the rust toolchain for now to keep CI green.
 * Enable verbose kbuild.
@emilio emilio disabled auto-merge April 4, 2025 14:53
@emilio emilio added this pull request to the merge queue Apr 4, 2025
Merged via the queue into rust-lang:main with commit 7eb87db Apr 4, 2025
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant