Workaround: Skip rustc book on i686

[JonathanBrouwer]

View all comments

Workaround for #158378 so we can get CI going again

r? @ghost

[JonathanBrouwer]

@bors try jobs=dist-i686-msvc

[Mark-Simulacrum]

r=me

[jhpratt]

@bors r=Mark-Simulacrum,jhpratt rollup=never p=1000

[rust-bors]

📌 Commit 7dd19f9 has been approved by Mark-Simulacrum,jhpratt

It is now in the queue for this repository.

[rust-bors]

💔 Test for 5647c58 failed: CI. Failed job:

• auto - i686-msvc-2 (web logs, enhanced plaintext logs)

[JonathanBrouwer]

@bors r=Mark-Simulacrum,jhpratt

[rust-bors]

📌 Commit 0b6be6b has been approved by Mark-Simulacrum,jhpratt

It is now in the queue for this repository.

[rust-bors]

💔 Test for 5dac7b2 failed: CI. Failed job:

• auto - aarch64-msvc-1 (web logs, enhanced plaintext logs)

[Mark-Simulacrum]

@bors retry

[56] Failure when receiving data from the peer (schannel: server closed abruptly (missing close_notify))

[rust-log-analyzer]

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

 TOOLSTATE_PUBLISH: 1
##[endgroup]
Updating crates.io index
error: failed to get `adler2` as a dependency of package `miniz_oxide v0.8.8`
... which satisfies dependency `miniz_oxide = "^0.8.5"` of package `flate2 v1.1.9`
... which satisfies dependency `flate2 = "^1.1.9"` of package `citool v0.1.0 (/home/runner/work/rust/rust/src/ci/citool)`
Caused by:
failed to load source for dependency `adler2`
Caused by:
unable to update registry `crates-io`
Caused by:
download of ad/le/adler2 failed
Caused by:
curl failed
Caused by:

[rust-log-analyzer]

A job failed! Check out the build log: (web)(plain enhanced)(plain)

Click to see the possible cause of the failure (guessed by this bot)

 NO_DOWNLOAD_CI_LLVM: 1
WIX: /c/a/rust/rust/wix
##[endgroup]
Updating crates.io index
error: failed to get `time` as a dependency of package `cookie_store v0.21.1`
... which satisfies dependency `cookie_store = "^0.21.1"` of package `ureq v3.0.8`
... which satisfies dependency `ureq = "^3"` of package `citool v0.1.0 (C:\a\rust\rust\src\ci\citool)`
Caused by:
failed to load source for dependency `time`
Caused by:

[jhpratt]

(still being tested; r-l-a is slow)

[jhpratt]

@bors treeclosed=5

Let's let the n=35 rollup run if this succeeds.

[rust-bors]

Tree closed for PRs with priority less than 5.

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 3h 24m 12s
Pushing 8e25b41 to main...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing f28ac76 (parent) -> 8e25b41 (this PR)

Test differences

Show 12 test diffs

Stage 0

• basic_broken: pass -> [missing] (J0)
• broken_fragment_local: pass -> [missing] (J0)
• broken_fragment_remote: pass -> [missing] (J0)
• broken_intra_doc_link: pass -> [missing] (J0)
• broken_redir: pass -> [missing] (J0)
• directory_link: pass -> [missing] (J0)
• redirect_loop: pass -> [missing] (J0)
• valid: pass -> [missing] (J0)

Additionally, 4 doctest diffs were found. These are ignored, as they are noisy.

Job group index

• J0: aarch64-msvc-2, i686-msvc-2, x86_64-msvc-2

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 8e25b4121d5ea29bef166b86173fb043782ffbff --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. i686-gnu-2: 53m 17s -> 1h 36m (+81.1%)
2. dist-powerpc64le-linux-musl: 1h 3m -> 1h 34m (+49.0%)
3. i686-gnu-1: 1h 38m -> 2h 21m (+43.2%)
4. dist-apple-various: 2h 27m -> 1h 30m (-38.9%)
5. dist-aarch64-apple: 2h 29m -> 1h 35m (-36.1%)
6. dist-sparcv9-solaris: 1h 34m -> 1h (-35.7%)
7. dist-x86_64-netbsd: 1h 27m -> 58m 57s (-32.3%)
8. x86_64-msvc-1: 1h 55m -> 2h 26m (+27.4%)
9. x86_64-rust-for-linux: 43m 26s -> 33m 25s (-23.1%)
10. dist-powerpc64-linux-musl: 1h 32m -> 1h 13m (-20.5%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (8e25b41): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.2%	[0.2%, 0.2%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -5.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-5.4%	[-5.4%, -5.4%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-5.4%	[-5.4%, -5.4%]	1

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 510.446s -> 503.101s (-1.44%)
Artifact size: 353.05 MiB -> 353.51 MiB (0.13%)