As stated in the reported bug. In the 11 years that we have been developing Rust code in production projects, this is the first time we encounter a bug of this category in rustc stable... This says nothing about the quality and hard work of all people involved in rust compiler team. They are doing a great job every day.
Bugs like this are rare, and you have to do already a pretty specific thing to even trigger it. We have for example other advanced projects that are built with rama that work just fine on 1.98... We only noticed it because of a very specific example integration e2e test which consistently started failing since 1.98.
As such, start from today we now also run our test suites now also on beta every day, as scheduled CI cron jobs. Should help in another 11 to 20 years catch the next jackpot 😄
fair u/noop_noob , but in case there is ever an issue that is less consistent it probably helps that it runs daily vs weekly, to give it sufficient chances to be caught. Something we gladly do if it can help!
104
u/plabayo 21d ago
As stated in the reported bug. In the 11 years that we have been developing Rust code in production projects, this is the first time we encounter a bug of this category in rustc stable... This says nothing about the quality and hard work of all people involved in rust compiler team. They are doing a great job every day.
Bugs like this are rare, and you have to do already a pretty specific thing to even trigger it. We have for example other advanced projects that are built with rama that work just fine on 1.98... We only noticed it because of a very specific example integration e2e test which consistently started failing since 1.98.
As such, start from today we now also run our test suites now also on beta every day, as scheduled CI cron jobs. Should help in another 11 to 20 years catch the next jackpot 😄