diff options
| author | bors <bors@rust-lang.org> | 2023-10-04 14:17:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-04 14:17:57 +0000 |
| commit | 2ffeb4636b4ae376f716dc4378a7efb37632dc2d (patch) | |
| tree | 5e6ef9d34ab9e62b58e3d6735fee3b18fa49d5e1 /tests/rustdoc-ui/custom_code_classes_in_docs-warning3.stderr | |
| parent | 65519f5fc0bcd8a47e547226bbc7498a2b9a59fb (diff) | |
| parent | c0a42cc7bdc7407427952a8fee01acec101e2544 (diff) | |
| download | rust-2ffeb4636b4ae376f716dc4378a7efb37632dc2d.tar.gz rust-2ffeb4636b4ae376f716dc4378a7efb37632dc2d.zip | |
Auto merge of #116381 - Mark-Simulacrum:drop-wasm32-unknown-emscripten, r=Kobzol
Remove wasm32-unknown-emscripten tests from CI This builder tested the wasm32-unknown-emscripten target, which is tier 2 (and so not eligible for testing). In the recent beta [promotion](https://github.com/rust-lang/rust/pull/116362#issuecomment-1744960904), 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.
Diffstat (limited to 'tests/rustdoc-ui/custom_code_classes_in_docs-warning3.stderr')
0 files changed, 0 insertions, 0 deletions