user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Disable dump-ice-to-disk on i686-pc-windows-msvc

Browse source 
Sometimes the middle frames of the ICE backtrace becomes `<unknown>` on
`i686-pc-windows-msvc` which then makes this test flaky.
This commit is contained in:
Jieyou Xu 2026-01-16 09:27:45 +08:00
parent 22c74ba918
commit 8dfb888812
No known key found for this signature in database
GPG key ID: 36D068BDB127FD95
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
tests/run-make/dump-ice-to-disk/rmake.rs
View file

@ -18,13 +18,16 @@
//! # Test history
//!
//! The previous rmake.rs iteration of this test was flaky for unknown reason on
//! `i686-pc-windows-gnu` *specifically*, so assertion failures in this test was made extremely
//! verbose to help diagnose why the ICE messages was different. It appears that backtraces on
//! `i686-pc-windows-gnu` specifically are quite unpredictable in how many backtrace frames are
//! involved.
//! `i686-pc-windows-gnu`, so assertion failures in this test was made extremely verbose to help
//! diagnose why the ICE messages was different. It appears that backtraces on `i686-pc-windows-gnu`
//! specifically are quite unpredictable in how many backtrace frames are involved.
//!
//! Disabled on `i686-pc-windows-msvc` as well, because sometimes the middle portion of the ICE
//! backtrace becomes `<unknown>`.
//@ ignore-cross-compile (exercising ICE dump on host)
//@ ignore-i686-pc-windows-gnu (unwind mechanism produces unpredictable backtraces)
//@ ignore-i686-pc-windows-msvc (sometimes partial backtrace becomes `<unknown>`)
use std::cell::OnceCell;
use std::path::{Path, PathBuf};