compiletest: Use //@ prefixes also for debuginfo test directives

[Enselic]

So that when we later add support for revisions we can use the same syntax for revisions as elsewhere (for #147426).

This also prevents people from making typos for commands since src/tools/compiletest/src/directives/directive_names.rs will catch such typos now.

Note that we add one FIXME for a non-trivial change for later:

// FIXME(#148097): Change `// cdb-checksimple_closure` to `//@ cdb-check:simple_closure`

TODO

• Triple-check that all tests still run and all directives are still applied. Done: compiletest: Use //@ prefixes also for debuginfo test directives #147799 (comment)

Zulip discussion

https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/.2F.2F.40.20syntax.20for.20debuginfo.20tests/with/545015582

[Enselic]

@bors try jobs=x86_64-msvc-1

[rust-bors]

☀️ Try build successful (CI)
Build commit: c89eb6c (c89eb6c72bc4a168b32b17a36f56df1e617c3cb3, parent: 51f5892019f8fb07864647d46c4eb577d3b0719f)

[Enselic]

@bors try jobs=x86_64-msvc-1

[rust-bors]

☀️ Try build successful (CI)
Build commit: 464c055 (464c055969e217e038285dbdafe6bcb4c174f8a0, parent: 17e7324d44c7b310b776302880fdd08d9252118a)

[Enselic]

x86_64-msvc-1 does not have cdb it seems, but I think aarch64 does:

@bors try jobs=aarch64-msvc-1

[rust-bors]

💔 Test for 8aa08e9 failed: CI. Failed jobs:

• try - aarch64-msvc-1 (web logs, extended logs)

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[Enselic]

#147760 is now merged, with what looks like an impressive number of conflicts.

Luckily they were easy to resolve mechanically.

[saethlin]

r? saethlin

@bors r+ rollup=never p=6 This will conflict with any change to the debuginfo tests

[bors]

📌 Commit 5b57d02 has been approved by saethlin

It is now in the queue for this repository.

[bors]

⌛ Testing commit 5b57d02 with merge b249b3d...

[bors]

💔 Test failed - checks-actions

[Zalathar]

I can't see raw logs, which means a runner probably flaked out.

@bors retry

[bors]

⌛ Testing commit 5b57d02 with merge 6840234...

[bors]

☀️ Test successful - checks-actions
Approved by: saethlin
Pushing 6840234 to main...

[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 d8a7534 (parent) -> 6840234 (this PR)

Test differences

Show 3 test diffs

3 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 6840234806e4a57e14112a1137783c885b7a23db --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-apple-various: 4310.5s -> 3326.1s (-22.8%)
2. dist-loongarch64-linux: 5296.8s -> 6414.3s (+21.1%)
3. tidy: 192.3s -> 159.5s (-17.1%)
4. x86_64-gnu-debug: 6622.1s -> 5999.4s (-9.4%)
5. aarch64-apple: 8545.1s -> 7748.8s (-9.3%)
6. x86_64-gnu-gcc: 3136.0s -> 2862.9s (-8.7%)
7. arm-android: 6151.6s -> 5631.7s (-8.5%)
8. i686-msvc-1: 10914.4s -> 10018.6s (-8.2%)
9. x86_64-msvc-ext3: 6490.5s -> 5971.9s (-8.0%)
10. dist-various-2: 2106.5s -> 2261.6s (+7.4%)

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 (6840234): comparison URL.

Overall result: ❌ regressions - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.1%	[0.1%, 0.1%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

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

Cycles

Results (primary -3.6%, secondary -4.0%)

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)	2.9%	[2.9%, 2.9%]	1
Improvements ✅ (primary)	-3.6%	[-10.9%, -1.8%]	15
Improvements ✅ (secondary)	-5.2%	[-9.0%, -2.1%]	6
All ❌✅ (primary)	-3.6%	[-10.9%, -1.8%]	15

Binary size

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

Bootstrap: 479.37s -> 469.478s (-2.06%)
Artifact size: 386.91 MiB -> 386.94 MiB (0.01%)