find_dep_kind_root tweaks

[nnethercote]

Two minor changes relating to find_dep_kind_root.

r? @SparrowLii

[rustbot]

SparrowLii is not on the review rotation at the moment.
They may take a while to respond.

[petrochenkov]

Needs a rebase after the QueryStackDeferred removal.
@rustbot author
r? @petrochenkov

[rustbot]

Reminder, once the PR becomes ready for a review, use @rustbot ready.

[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.

[nnethercote]

I rebased. Thanks for taking the review.

@rustbot ready

[petrochenkov]

@bors r+

[rust-bors]

📌 Commit ddd1a69 has been approved by petrochenkov

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: petrochenkov
Duration: 3h 10m 29s
Pushing fd26499 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 620e36a (parent) -> fd26499 (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 fd2649988fdc91e056ddd316865d33e812f48a0e --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-aarch64-apple: 2h 1m -> 1h 31m (-24.1%)
2. aarch64-apple: 3h 4m -> 2h 33m (-17.1%)
3. x86_64-gnu-debug: 2h 9m -> 1h 55m (-10.8%)
4. x86_64-msvc-ext3: 1h 42m -> 1h 53m (+10.5%)
5. dist-x86_64-illumos: 1h 36m -> 1h 46m (+10.3%)
6. x86_64-gnu-llvm-21-3: 2h 3m -> 1h 52m (-9.3%)
7. x86_64-gnu-miri: 1h 29m -> 1h 21m (-8.9%)
8. i686-gnu-2: 1h 41m -> 1h 32m (-8.8%)
9. tidy: 2m 41s -> 2m 27s (-8.5%)
10. i686-gnu-nopt-1: 2h 21m -> 2h 10m (-7.8%)

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

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (secondary -2.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)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.0%	[-2.6%, -1.1%]	3
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: 483.729s -> 481.843s (-0.39%)
Artifact size: 396.86 MiB -> 396.85 MiB (-0.00%)