-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Random compiler errors when running tests on my NES Emulator project #112479
Comments
I think you truncated the important part, the helpful error message is at the top of an ICE. Can you edit that in? |
This looks like an incremental unstable fingerprints ICE on |
Hey guys, I managed to recreate the issue and have pasted the full log. The code that produces the error is the latest commit in the NESEmulator repo on my profile. |
It seems some commits were added to the repository since your message was posted, did you mean f3779700c76479bf38653df26291c29ed4e2b5b1 maybe ? |
The actual commit itself is irrelevant. The issue seems to occur at
random (up to and including the latest commit), and it gets fixed upon
cargo clean and cargo rebuild.
The issue itself occurs when running cargo build or cargo test.
Hope this helps!
…On Mon, 12 Jun 2023, 08:36 Rémy Rakic, ***@***.***> wrote:
I managed to recreate the issue and have pasted the full log. The code
that produces the error is the latest commit in the NESEmulator repo on my
profile.
It seems some commits were added to the repository since your message was
posted, did you mean f3779700c76479bf38653df26291c29ed4e2b5b1
<https://urldefense.com/v3/__https://github.com/MWJones96/NESEmulator/commit/f3779700c76479bf38653df26291c29ed4e2b5b1__;!!LIr3w8kk_Xxm!tneIRkMDcwPDOuoZsawMy1ge_ra7vxxTJ6Wj8DAbZkTmALqAEqFMhcGlXnuatGwejz0sR8X2zt_lBKEPDBewBRXC$>
maybe ?
Do you also have the commands to run so we can reproduce the issue ?
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/rust-lang/rust/issues/112479*issuecomment-1586754324__;Iw!!LIr3w8kk_Xxm!tneIRkMDcwPDOuoZsawMy1ge_ra7vxxTJ6Wj8DAbZkTmALqAEqFMhcGlXnuatGwejz0sR8X2zt_lBKEPDLe6fcnR$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ACWL354UKRB3FDDB25YASYDXK3BI3ANCNFSM6AAAAAAZBH7RWY__;!!LIr3w8kk_Xxm!tneIRkMDcwPDOuoZsawMy1ge_ra7vxxTJ6Wj8DAbZkTmALqAEqFMhcGlXnuatGwejz0sR8X2zt_lBKEPDLKMj23l$>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I have observed a similar issue in a private repository surrounding the usage of
|
I'll add that I'm on the latest stable toolchain version (1.70.0). I'm downgrading to older versions and testing because it seems like this used to work. |
I can confirm that this seems to work fine on 1.69.0 and doesn't work on 1.70.0. This seems like some kind of regression. The specific steps I can use to reproduce.
It seems that the failures happen the first time a mock method gets used in the build where it wasn't used in the previous (and uncleaned) build. I'm assuming this is the same issue that @MWJones96 is having as well - due to the similarity of the stack traces. Can you test with a similiar procedure and see if you observe the same behavior? |
The issue also seems to not occur with the latest nightly compiler version.
|
It also doesn't seem to occur for me on the latest beta compiler version 🎉
|
Hey all,
Thanks for looking into this. Is there any further information you need
from me?
…On Fri, 23 Jun 2023, 19:14 Jonathan Hood, ***@***.***> wrote:
It *also* doesn't seem to occur for me on the latest beta compiler
version 🎉
***@***.***:~/projects/tango-tango/trig_daemon$ rustc --version --verbose
rustc 1.71.0-beta.3 (78a6ac0 2023-06-08)
binary: rustc
commit-hash: 78a6ac0
commit-date: 2023-06-08
host: aarch64-unknown-linux-gnu
release: 1.71.0-beta.3
LLVM version: 16.0.4
—
Reply to this email directly, view it on GitHub
<https://urldefense.com/v3/__https://github.com/rust-lang/rust/issues/112479*issuecomment-1604665796__;Iw!!LIr3w8kk_Xxm!q9D9GMKOKQoU2QErPon2v03G_cy4Y8SVfZoG4WXHvXkmVCAycq5pp3ErutAoTc-KjVZ15EkxsNJkScsDsVIHgjI0$>,
or unsubscribe
<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ACWL353KGVXOEHWXIRIZPSTXMXMGTANCNFSM6AAAAAAZBH7RWY__;!!LIr3w8kk_Xxm!q9D9GMKOKQoU2QErPon2v03G_cy4Y8SVfZoG4WXHvXkmVCAycq5pp3ErutAoTc-KjVZ15EkxsNJkScsDsSct0hg6$>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
there was a known issue with mir_built that was fixed on beta, correct. I'm going to close this as it seems like it was fixed. Thank you for the report and investigation anyways! |
Code
No specific code, appears to occur randomly. I am writing an emulator. It appears to fix itself with a clean + rebuild.
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: