Cycle error involving Freeze
when testing time
crate
#119273
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
C-bug
Category: This is a bug.
I-cycle
Issue: A query cycle occurred while none was expected
P-medium
Medium priority
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
For roughly a month, I have been getting an error in CI when performing code coverage. This is due to a stderr diff (I'm using
trybuild
). By itself, that is acceptable breakage, but the cause is a cycle error. Given the most recent successful and earliest failing CI runs, I bisected the compiler. The results are below. I have not attempted to minimize the error in any way.In my opinion, a cycle error like this should be a proper ICE in terms of diagnostics, which would tell the user to file an issue. I only know to do this because of my involvement with rustc.
This change will land on stable in just a few days. I have reproduced it on the 1.75.0 binary from the pre-release server.
cc @compiler-errors as author of the PR apparently causing regression (#117418)
The diff in question:
@rustbot label +C-bug +regression-from-stable-to-beta +T-compiler
searched nightlies: from nightly-2023-10-20 to nightly-2023-11-19
regressed nightly: nightly-2023-11-08
searched commit range: 189d6c7...7adc89b
regressed commit: 504f63e
bisected with cargo-bisect-rustc v0.6.7
Host triple: x86_64-unknown-linux-gnu
Reproduce with:
./test.sh
contains:The text was updated successfully, but these errors were encountered: