-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
json test_read_{list,object}_streaming are flaky on 32-bit #14064
Comments
See rust-lang#14064 for some rationale, but the basic idea is that I suspect that there is an LLVM codegen bug somewhere, and I'm not entirely sure why it's happening intermittently rather than deterministically... cc rust-lang#14064
From #14083 (auto-linux-32-nopt-t failure log), it may be flaky on other 32-bit machines. |
Ah yes, sorry, I meant to update this bug. I have noticed and reproduced this on 32-bit platforms in general. |
It was thought that these failures only happened on windows, turns out they happen on any 32-bit machine. cc rust-lang#14064
It was thought that these failures only happened on windows, turns out they happen on any 32-bit machine. cc #14064
visiting for triage Can confirm these tests are still ignored:
I unfortunately don't have a 32 bit window machine to test them on though :( |
Triage: same as @frewsxcv , These are still presently ignored, but I don't have the proper machinery. @alexcrichton , should we maybe try removing the ignore, and letting bors take a look? If it was a bug in LLVM, well, a lot has changed since 2014.... |
Sure, I'd be game for unignoring them |
…richton Unignore the json tests on 32-bit platforms cc rust-lang#14064 r? @alexcrichton
#36123 unignored these, so this can [probably] be closed. |
…r=lnicola minor: Simplify `is_exit` check in `lsp-server` (this is what `socket` one does)
These tests have been seen to be flaky on 32-bit with a very obscure error:
I find these error messages curious. These tests only fail on windows, and they only fail with optimization turned on. I suspect an LLVM bug here, but I haven't confirmed it. For now I'm going to ignore these tests on windows.
The text was updated successfully, but these errors were encountered: