Jon Ross-Perkins 83413479d7 Move some of the test information to TIP lines (#4007) ...

This has is a nice-to-have for me. Frequently I want to run a specific
test, and end up digging through output to be able to copy-paste the run
line. This uses TIP lines to inject the command into the file when using
AUTOUPDATE.

Note, one of the reasons I want this is because "bazel test
//toolchain/testing:file_test --test_output=all" has been regularly
exceeding bazel's output limit for me (workaround is either opening the
output file or specifying an obscure output limit flag), making it a
little harder for me to get the commands. However, frequently I'm adding
a file and want to iterate on it, so that's really the use case I have
in mind here.

2024-06-04 17:57:23 +00:00

..

fail_bad_name.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

fail_empty.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

fail_missing_type.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

fail_no_semi.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

let_tuple.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

let.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00

missing_value.carbon

Move some of the test information to TIP lines (#4007)

2024-06-04 17:57:23 +00:00