Closed
Description
A MSVC x86_64 bors job has failed on two unrelated PRs (#60026, #66170) with the same error:
2019-11-12T18:01:21.3370489Z memory allocation of 4294967304 bytes failed[RUSTC-TIMING] hex test:false 3.438
2019-11-12T18:01:21.3472541Z error: could not compile `hex`.
2019-11-12T18:01:22.8915944Z [RUSTC-TIMING] glob test:false 1.984
2019-11-12T18:01:22.9032050Z error: build failed
2019-11-12T18:01:22.9081592Z command did not execute successfully: "D:\\a\\1\\s\\build\\x86_64-pc-windows-msvc\\stage0\\bin\\cargo.exe" "build" "-Zconfig-profile" "--target" "x86_64-pc-windows-msvc" "-Zbinary-dep-depinfo" "-j" "2" "--release" "--locked" "--color" "always" "--manifest-path" "D:\\a\\1\\s\\src/tools/cargo\\Cargo.toml" "--features" "rustc-workspace-hack/all-static" "--message-format" "json-render-diagnostics"
2019-11-12T18:01:22.9082199Z expected success, got: exit code: 101
2019-11-12T18:01:22.9082199Z expected success, got: exit code: 101
2019-11-12T18:01:23.0062715Z failed to run: D:\a\1\s\build\bootstrap\debug\bootstrap dist
In both cases, cargo build attempted to allocate several GB of memory while compiling the hex crate. One of these failures was in the dist-x86_64-msvc job, and the other was in x86_64-msvc-cargo.
This failure appears to be spurious: a previous version of #60026 passed the same job.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Area: Spurious failures in builds (spuriously == for no apparent reason)Issue: Problems and improvements with respect to memory usage during compilation.High priorityRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the infrastructure team, which will review and decide on the PR/issue.Performance or correctness regression from stable to nightly.