-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to rust 1.80.0 #32896
Update to rust 1.80.0 #32896
Conversation
Signed-off-by: Hayashi Mikihiro <[email protected]>
Signed-off-by: Hayashi Mikihiro <[email protected]>
rust-lang/rust#124047 Signed-off-by: Hayashi Mikihiro <[email protected]>
rust-lang/rust#123016 Signed-off-by: Hayashi Mikihiro <[email protected]>
rust-lang/rust#124955 Signed-off-by: Hayashi Mikihiro <[email protected]>
rust-lang/rust#125410 Signed-off-by: Hayashi Mikihiro <[email protected]>
Signed-off-by: Hayashi Mikihiro <[email protected]>
Signed-off-by: Hayashi Mikihiro <[email protected]>
Signed-off-by: Hayashi Mikihiro <[email protected]>
Do you have windows machine/will to investigate windows problem, or would you like for someone else to take over? |
I don't have a Windows machine. I only investigate Github Actions. I can only reproduce in resource_thread::test_exit release build on ver1.79&1.80. I would take me a lot of time to fix, as it is too difficult to reproduce in debug build. I would like to request a takeover. |
Are you saying that debug builds works, but release don't?
So 1.79 is bad? |
Yes, I do. In debug build worked also warning are not occur.
Yes, in my view, 1.79 is bad around |
nightly-2024-04-05 is good
I did multiple runs to make get confidence in results (as this is flaky error). |
I used Apparently caused by rust-lang/rust@6f83750, I believe it's caused by rust-lang/rust#119224 |
This comment was marked as resolved.
This comment was marked as resolved.
I think this happens because we panic in drop of |
🔨 Triggering try run (#10217246405) for Windows |
It's dirty but it worked on 2000 runs Signed-off-by: sagudev <[email protected]>
✨ Try run (#10217246405) succeeded. |
I believe panic in panic being a hard unrecoverable abort is intentional in newer rustc versions. So I suspect we'll need to change the code to not do that. |
The problem is that we panic in the first place (both panics actually happens in same place if I am reading traces correctly). Anyway given that we have workaround for #32912 (which is just sleeping to wait for transmission to finish, as the code that checks for transmission finish is panicking), I think we do not need to block landing this PR on #32912. |
* Update for nix Signed-off-by: Hayashi Mikihiro <[email protected]> * Update to Rust 1.80.0 Signed-off-by: Hayashi Mikihiro <[email protected]> * Rename to BindingMode from BindingAnnotation rust-lang/rust#124047 Signed-off-by: Hayashi Mikihiro <[email protected]> * Remove TypeVariableOriginKind rust-lang/rust#123016 Signed-off-by: Hayashi Mikihiro <[email protected]> * Remove TypeVariableOrigin rust-lang/rust#124955 Signed-off-by: Hayashi Mikihiro <[email protected]> * Remove LintDiagnostic::msg rust-lang/rust#125410 Signed-off-by: Hayashi Mikihiro <[email protected]> * common.rs fmt mistake indents Signed-off-by: Hayashi Mikihiro <[email protected]> * trace_in_no_trace.rs remove mistake space Signed-off-by: Hayashi Mikihiro <[email protected]> * trace_in_no_trace.rs remove mistake head space Signed-off-by: Hayashi Mikihiro <[email protected]> * Workaround for servo#32912 It's dirty but it worked on 2000 runs Signed-off-by: sagudev <[email protected]> --------- Signed-off-by: Hayashi Mikihiro <[email protected]> Signed-off-by: sagudev <[email protected]> Co-authored-by: Samson <[email protected]>
I would create a new pull request for commits failed in PR #32889 .
rustc library had some changes in 1.79 & 1.80.
LazyLock
is part of standard library in 1.80Rust1.80 can replace from
lazy_static
&once_cell::sync::Lazy
tostd::LazyLock
.I would suggest updating to rust1.80 as the first step, with replace to
LazyLock
later../mach build -d
does not report any errors./mach test-tidy
does not report any errors