Revert "bump rust to 1.82.0 (#3308)" #3320
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
I'm experiencing SIGILL crashes due to invalid opcodes. Maybe it's related to the recent rust 1.82.0 upgrade? Getting a revert PR going so it'll be ready as needed.
I started up two nodes with master, just after the upgrade of rust to 1.82.0 (
f8b33755f6b08d03f020bbeae4fd9724f2a407d3). Both nodes crashed. Upon investigating the syslog, both had:I built the binaries locally on each machine. I retried on one of the machines three times, and got the same crash each time. I then kept the same commit checked out and built with rust 1.81.0 and there were no more crashes.
Summary of Changes
This reverts commit ed5e30d.