Remove wasm32-unknown-emscripten tests from CI

[Mark-Simulacrum]

This builder tested the wasm32-unknown-emscripten target, which is tier 2 (and so not eligible for testing). In the recent beta promotion, we ran into a problem with this target: emscripten doesn't support passing environment variables into the std environment, so we can't enable RUSTC_BOOTSTRAP for libtest in order to pass -Zunstable-options.

We worked around this for the beta/stable branches, but given this problem, and its tier 2 status, just dropping the target's tests entirely seems warranted. Downgrading to tier 3 may also be a good idea, but that is a separate conversation not proposed here.

[rustbot]

r? @Kobzol

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

[Kobzol]

Tier 2 claims:

"Tier 2 targets can be thought of as "guaranteed to build"

Doesn't that mean that we should still build (or at least check) it on CI, just without running tests?

(I also think this target should be demoted to tier 3 though).

[cuviper]

Doesn't that mean that we should still build (or at least check) it on CI, just without running tests?

The target is still built on dist-various-1 and shipped from there.

[Kobzol]

The target is still built on dist-various-1 and shipped from there.

I see, thanks!

I noticed that some of the other builders (like asmjs) were moved to the disabled directory instead of being deleted. Is there some policy regarding this?

[Mark-Simulacrum]

Not that I know of. I don't see any significant benefit to keeping the files around, they're in git history anyway.

[Kobzol]

Ok. In that case, good riddance!

@bors r+

[bors]

📌 Commit c0a42cc has been approved by Kobzol

It is now in the queue for this repository.

[bors]

⌛ Testing commit c0a42cc with merge 2ffeb46...

[bors]

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

[rust-timer]

Finished benchmarking commit (2ffeb46): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.7%	[-0.8%, -0.7%]	3
Improvements ✅ (secondary)	-0.6%	[-0.6%, -0.6%]	3
All ❌✅ (primary)	-0.7%	[-0.8%, -0.7%]	3

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

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: 623.638s -> 622.556s (-0.17%)
Artifact size: 272.00 MiB -> 272.00 MiB (-0.00%)