Skip to content
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

Tracking Issue for spurious mingw CI failures #133958

Open
jieyouxu opened this issue Dec 6, 2024 · 3 comments
Open

Tracking Issue for spurious mingw CI failures #133958

jieyouxu opened this issue Dec 6, 2024 · 3 comments
Labels
A-CI Area: Our Github Actions CI C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC CI-spurious-fail-mingw CI spurious failure: target env mingw O-windows-gnu Toolchain: GNU, Operating system: Windows T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@jieyouxu
Copy link
Member

jieyouxu commented Dec 6, 2024

The spurious mingw failures might be related to #127883, but for the purpose of tracking, we should delineate the two general categories separately to avoid conflating them.

Please feel free to update specific classifications of kinds of spurious mingw failures.

Known problems

Misc

Label: CI-spurious-fail-mingw CI spurious failure: target env mingw

@jieyouxu jieyouxu added A-CI Area: Our Github Actions CI C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC CI-spurious-fail-mingw CI spurious failure: target env mingw O-windows-gnu Toolchain: GNU, Operating system: Windows T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Dec 6, 2024
@workingjubilee
Copy link
Member

workingjubilee commented Feb 3, 2025

We got a new spurious failure for x86_64-mingw-1 as of #135265 (comment)

Building stage1 library artifacts (x86_64-pc-windows-gnu)
     Compiling shlex v1.3.0
     Compiling core v0.0.0 (D:\a\rust\rust\library\core)
     Compiling libc v0.2.169
     Compiling object v0.36.7
  [RUSTC-TIMING] shlex test:false 0.251
     Compiling cc v1.2.0
  [RUSTC-TIMING] build_script_build test:false 0.317
     Compiling std v0.0.0 (D:\a\rust\rust\library\std)
  [RUSTC-TIMING] build_script_build test:false 0.493
     Compiling windows-targets v0.0.0 (D:\a\rust\rust\library\windows_targets)
  [RUSTC-TIMING] windows_targets test:false 0.071
  [RUSTC-TIMING] build_script_build test:false 0.307
  [RUSTC-TIMING] cc test:false 1.913
     Compiling compiler_builtins v0.1.143
  [RUSTC-TIMING] build_script_build test:false 0.601
     Compiling rustc-std-workspace-core v1.99.0 (D:\a\rust\rust\library\rustc-std-workspace-core)
  [RUSTC-TIMING] rustc_std_workspace_core test:false 0.046
  [RUSTC-TIMING] libc test:false 0.130
     Compiling alloc v0.0.0 (D:\a\rust\rust\library\alloc)
     Compiling cfg-if v1.0.0
  [RUSTC-TIMING] cfg_if test:false 0.053
     Compiling unwind v0.0.0 (D:\a\rust\rust\library\unwind)
  [RUSTC-TIMING] unwind test:false 0.114
     Compiling memchr v2.7.4
  [RUSTC-TIMING] memchr test:false 3.598
     Compiling adler2 v2.0.0
  [RUSTC-TIMING] adler2 test:false 0.311
     Compiling rustc-demangle v0.1.24
  [RUSTC-TIMING] core test:false 36.663
  [RUSTC-TIMING] compiler_builtins test:false 8.212
  [RUSTC-TIMING] rustc_demangle test:false 2.306
     Compiling rustc-std-workspace-alloc v1.99.0 (D:\a\rust\rust\library\rustc-std-workspace-alloc)
     Compiling panic_unwind v0.0.0 (D:\a\rust\rust\library\panic_unwind)
     Compiling panic_abort v0.0.0 (D:\a\rust\rust\library\panic_abort)
  [RUSTC-TIMING] panic_abort test:false 0.085
     Compiling gimli v0.31.1
  
  thread 'main' has overflowed its stack
  [RUSTC-TIMING] rustc_std_workspace_alloc test:false 0.178
  error: could not compile `rustc-std-workspace-alloc` (lib)
  
  Caused by:
    process didn't exit successfully: `D:\a\rust\rust\build\bootstrap\debug\rustc 'D:\a\rust\rust\build\bootstrap\debug\rustc' --crate-name rustc_std_workspace_alloc --edition=2021 'library\rustc-std-workspace-alloc\lib.rs' --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C codegen-units=1 -C debug-assertions=on --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=69a77775622bba16 -C extra-filename=-d9491a0d5cbf2563 --out-dir 'D:\a\rust\rust\build\x86_64-pc-windows-gnu\stage1-std\x86_64-pc-windows-gnu\release\deps' --target x86_64-pc-windows-gnu -L 'dependency=D:\a\rust\rust\build\x86_64-pc-windows-gnu\stage1-std\x86_64-pc-windows-gnu\release\deps' -L 'dependency=D:\a\rust\rust\build\x86_64-pc-windows-gnu\stage1-std\release\deps' --extern 'alloc=D:\a\rust\rust\build\x86_64-pc-windows-gnu\stage1-std\x86_64-pc-windows-gnu\release\deps\liballoc-1e3516e1b97121d6.rmeta' -Csymbol-mangling-version=legacy '--check-cfg=cfg(feature,values(any()))' -Zunstable-options '--check-cfg=cfg(bootstrap)' -Zmacro-backtrace -Csplit-debuginfo=packed -Cprefer-dynamic -Zinline-mir -Zinline-mir-preserve-debug -Zmir_strip_debuginfo=locals-in-tiny-functions -Alinker-messages -Cembed-bitcode=yes -Cforce-frame-pointers=yes '-Zcrate-attr=doc(html_root_url="https://doc.rust-lang.org/nightly/")' -Z binary-dep-depinfo -L 'native=D:\a\rust\rust\build\x86_64-pc-windows-gnu\stage1-std\x86_64-pc-windows-gnu\release\build\compiler_builtins-c2690e8fa265cdad\out'` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)
  warning: build failed, waiting for other jobs to finish...
  [RUSTC-TIMING] panic_unwind test:false 0.183
  [RUSTC-TIMING] alloc test:false 8.813
  [RUSTC-TIMING] gimli test:false 6.039

@ChrisDenton
Copy link
Member

I guess it is possible something is pushing close to the limits of the stack and just sometimes it tips over the edge. Though I'm not sure why that would be.

@madsmtm
Copy link
Contributor

madsmtm commented Feb 25, 2025

Another one in #133832 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-CI Area: Our Github Actions CI C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC CI-spurious-fail-mingw CI spurious failure: target env mingw O-windows-gnu Toolchain: GNU, Operating system: Windows T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants