@WG-prioritization/alerts issue #76466 has been requested for prioritization.
based on Santiago's heuristics :-P this should probably be tagged as
P-critical even if it's Tier-2. The reporter also kindly did some bisecting and we have a candidate culprit (https://github.com/rust-lang/rust/commit/5180f3da5fd72627a8d38558ad1297df38793acd)
I'm slightly confused and curious by how that commit can cause that error :thinking:
@apiraino that’s only the commit of the culprit nightly
do you mean that there may be another bug behind (in some other component, such as the
lld linker as the reporter suggests) that nightly?
@apiraino what @LeSeulArtichaut suggested is that, that's the commit with which the nightly version they are using was generated but it's not the offending commit
we would need to run cargo-bisect-rustc to find out which one is the offending commit
I'm not sure about the priority of this one but could totally be
non working wasm seems bad to me
but it may be windows only
we would need someone to find out a bit more info
@WG-prioritization this is one of the last issues to prioritize
in my opinion
fwiw I had voted for a p-critical (out of caution). Perhaps a closer look by the relevant team could possibly help
ping about this. Suggestions?
i'm tempted to mark this p-high till we know the commit causing it, but critical is fine as well
right, it will get some attention during the meeting and probably help finding someone to give a closer look. Not a lot more to add at this time, unfortunately.
Issue #76466's prioritization request has been removed.
Just ran bisect and the commit range from 663d2f5 to 5180f3d passed with no issues. Re-reading through the issue it may be on a 32-bit Windows host instead of 64-bit Windows host
I noticed in the
rustc --version --verbose output the host is listed as
host: i686-pc-windows-msvc instead of
I will run bisect on my Linux machine to check there as well but it's possible this is only a regression on 32-bit Windows machines.
Same result on my 64-bit Linux machine. bisect-rustc is passing with no issues
@Mason Stallmo maybe comment on the issue with all that information?
great job @Mason Stallmo :thumbs_up: