Files
rust/tests/ui
bors 8ccb78e0d5 Auto merge of #125579 - Noratrieb:print-host, r=davidtwco
Add `--print host-tuple` to print host target tuple

People often parse `-vV` output to get to the host tuple, which is annoying to do. It's easier to just get it directly.

I called it "host-tuple" instead of "host" because it's clearer that it's just the target name. I'm open to different names, but I think this one is fine.

a quick GitHub search for `'^host` reveals many instances of people doing the parsing, for example:

https://github.com/japaric/xargo/blob/68e0ca57cd90837fe02f262f074182f9cfeb6227/README.md?plain=1#L369
https://github.com/taiki-e/setup-cross-toolchain-action/blob/0e38473b0c562d6db19a98d3ec20a80f7ac189ae/main.sh#L96
https://github.com/taiki-e/cargo-llvm-cov/blob/8a3553b86551eabf9c30c060b1f72a5bbccb98c6/README.md?plain=1#L625
https://github.com/SiliconLabs/cpc-nvm3/blob/43f3ec39709b30700ef7f39d91fa647974323bf1/do.sh#L35

needs a compiler FCP. I could also do an MCP but I think just an FCP here makes the most sense.
2024-11-02 23:04:42 +00:00
..
2024-10-28 14:20:28 +11:00
2024-07-18 00:00:04 +00:00
2024-08-10 12:07:17 +02:00
2024-11-01 16:53:36 +08:00
2024-11-02 16:58:50 +00:00
2024-09-20 10:02:14 -07:00
2024-04-21 15:43:43 -03:00
2024-11-01 01:46:23 +00:00
2024-08-10 12:07:17 +02:00
2024-09-20 01:20:10 +03:00
2024-09-05 06:37:38 -04:00
2024-09-15 09:51:32 +02:00
2024-11-02 03:08:04 +00:00
2024-10-30 16:47:47 -07:00
2024-07-12 03:22:32 +00:00
2024-10-30 16:47:47 -07:00
2024-09-20 10:02:14 -07:00
2024-04-29 14:53:38 +02:00
2024-10-30 16:47:47 -07:00
2024-10-31 13:12:22 +08:00
2024-10-24 04:33:14 +08:00
2024-10-28 14:20:28 +11:00
2024-08-18 19:46:53 +02:00
2024-05-28 12:31:12 +02:00
2024-09-27 14:40:38 +01:00
2024-10-30 16:47:47 -07:00
2024-11-02 21:29:59 +01:00
2024-10-22 12:55:16 +00:00
2024-08-03 07:57:31 -04:00
2024-10-12 13:01:36 +02:00
2024-10-11 11:30:08 -04:00
2024-10-30 10:48:08 +00:00
2024-11-02 03:08:04 +00:00
2024-10-28 14:12:17 +08:00
2024-11-02 16:58:50 +00:00
2024-10-28 14:20:28 +11:00
2024-10-28 14:20:28 +11:00
2024-06-25 18:06:22 +02:00
2024-10-30 16:47:47 -07:00

UI Tests

This folder contains rustc's UI tests.

Test Directives (Headers)

Typically, a UI test will have some test directives / headers which are special comments that tell compiletest how to build and intepret a test.

As part of an on-going effort to rewrite compiletest (see https://github.com/rust-lang/compiler-team/issues/536), a major change proposal to change legacy compiletest-style headers // <directive> to ui_test-style headers //@ <directive> was accepted (see https://github.com/rust-lang/compiler-team/issues/512.

An example directive is ignore-test. In legacy compiletest style, the header would be written as

// ignore-test

but in ui_test style, the header would be written as

//@ ignore-test

compiletest is changed to accept only //@ directives for UI tests (currently), and will reject and report an error if it encounters any comments // <content> that may be parsed as an legacy compiletest-style test header. To fix this, you should migrate to the ui_test-style header //@ <content>.