Rename mingw-* CI jobs to pr-*

[ChrisDenton]

The name mingw confuses people because these CI jobs now do much more than just cross-compile to mingw.

This is basically a find/replace. I chose the name pr- because it's job is to do general PR checks,

[rustbot]

r? @jdno

rustbot has assigned @jdno.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

There are changes to the tidy tool.

cc @jieyouxu

The rustc-dev-guide subtree was changed. If this PR only touches the dev guide consider submitting a PR directly to rust-lang/rustc-dev-guide otherwise thank you for updating the dev guide with your changes.

cc @BoxyUwU, @jieyouxu, @Kobzol, @tshepang

[workingjubilee]

Run set +e
info: removing rustup home
info: removing cargo home
info: removing rustup binaries
info: rustup is uninstalled
Invalid image: pr-check-tidy
Error: Process completed with exit code 1.

[ChrisDenton]

oh, I think having "mingw" in the name might be load-bearing...

[Kobzol]

Heh, I was just thinking about this today :)

You need to rename the directory with the Dockerfile.

[ChrisDenton]

Doh! That's totally obvious now that you mentioned it 😅

[Kobzol]

r? kobzol

[Kobzol]

Thanks!

@bors r+ rollup=never

(I want to make sure that there are no test changes

[bors]

📌 Commit 6671d9b has been approved by Kobzol

It is now in the queue for this repository.

[bors]

⌛ Testing commit 6671d9b with merge d612081...

[bors]

☀️ Test successful - checks-actions
Approved by: Kobzol
Pushing d612081 to master...

[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 6268d0a (parent) -> d612081 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard d6120810e56387730b2e86115471354c8084ca4a --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. dist-x86_64-apple: 10500.4s -> 7105.0s (-32.3%)
2. aarch64-gnu-debug: 4076.7s -> 3645.3s (-10.6%)
3. i686-gnu-2: 6014.6s -> 5470.6s (-9.0%)
4. x86_64-gnu-tools: 3655.2s -> 3325.1s (-9.0%)
5. x86_64-apple-1: 7617.4s -> 6945.3s (-8.8%)
6. x86_64-gnu-miri: 4914.5s -> 4491.5s (-8.6%)
7. dist-apple-various: 6144.3s -> 6669.0s (8.5%)
8. x86_64-gnu-debug: 5755.0s -> 5267.4s (-8.5%)
9. x86_64-rust-for-linux: 2778.8s -> 2545.4s (-8.4%)
10. i686-gnu-nopt-1: 7815.5s -> 7217.7s (-7.6%)

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 (d612081): 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 (secondary -0.7%)

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)	-	-	0
Improvements ✅ (secondary)	-0.7%	[-0.7%, -0.7%]	1
All ❌✅ (primary)	-	-	0

Cycles

Results (secondary -1.2%)

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.4%	[0.4%, 0.5%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.0%	[-3.5%, -0.4%]	6
All ❌✅ (primary)	-	-	0

Binary size

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

Bootstrap: 462.879s -> 461.527s (-0.29%)
Artifact size: 372.11 MiB -> 372.16 MiB (0.01%)