update which targets we test Miri on

[RalfJung]

I hope this doesn't cost too much time; running only the "pass" tests should be reasonably fast (1-2 minutes on my system).

Fixes#117167

[rustbot]

r? @Mark-Simulacrum

(rustbot has picked a reviewer for you, use r? to override)

[Mark-Simulacrum]

@bors r+ rollup=iffy

[bors]

📌 Commit a783f39 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit a783f39 with merge 4ae8641...

[bors]

💔 Test failed - checks-actions

[RalfJung]

error: cannot produce cdylib for cdylib v0.1.0 (C:\a\rust\rust\src\tools\miri\test-cargo-miri\cdylib) as the target i686-unknown-linux-gnu does not support these crate types

That is very strange. Is the cargo/rustc we have on Windows CI somehow restricted in terms of its cross-target support? On Miri CI we have a Windows host run Miri tests for a Linux target just fine.

I guess we don't need to run the cargo-miri smoke test, let's see if the rest works
@bors r=Mark-Simulacrum

[bors]

📌 Commit 1b3fbbb has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit 1b3fbbb with merge 1a2b2e7...

[bors]

💔 Test failed - checks-actions

[RalfJung]

@bors r=Mark-Simulacrum

[bors]

📌 Commit b48adef has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[bors]

⌛ Testing commit b48adef with merge e6e931d...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing e6e931d to master...

[rust-timer]

Finished benchmarking commit (e6e931d): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	1.9%	[1.9%, 1.9%]	1
Regressions ❌ (secondary)	2.2%	[2.2%, 2.2%]	1
Improvements ✅ (primary)	-1.0%	[-1.0%, -1.0%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.4%	[-1.0%, 1.9%]	2

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 636.162s -> 635.955s (-0.03%)
Artifact size: 304.48 MiB -> 304.44 MiB (-0.01%)