Skip to content

Add #[rustc_clean(loaded_from_disk)] to assert loading of query result #92179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 3, 2022

Conversation

Aaron1011
Copy link
Member

Currently, you can use #[rustc_clean] to assert to that a particular
query (technically, a DepNode) is green or red. However, a green
DepNode does not mean that the query result was actually deserialized
from disk - we might have never re-run a query that needed the result.

Some incremental tests are written as regression tests for ICEs that
occured during query result decoding. Using
#[rustc_clean(loaded_from_disk="typeck")], you can now assert
that the result of a particular query (e.g. typeck) was actually
loaded from disk, in addition to being green.

Currently, you can use `#[rustc_clean]` to assert to that a particular
query (technically, a `DepNode`) is green or red. However, a green
`DepNode` does not mean that the query result was actually deserialized
from disk - we might have never re-run a query that needed the result.

Some incremental tests are written as regression tests for ICEs that
occured during query result decoding. Using
`#[rustc_clean(loaded_from_disk="typeck")]`, you can now assert
that the result of a particular query (e.g. `typeck`) was actually
loaded from disk, in addition to being green.
@rustbot rustbot added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Dec 21, 2021
@rust-highfive
Copy link
Contributor

r? @petrochenkov

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 21, 2021
@Aaron1011
Copy link
Member Author

@bors try @rust-timer queue

@rust-timer
Copy link
Collaborator

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

@rustbot rustbot added the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Dec 21, 2021
@bors
Copy link
Collaborator

bors commented Dec 21, 2021

⌛ Trying commit f1d6823 with merge 2214d3e77bea8be80a245351159c1781a52d7f71...

@bors
Copy link
Collaborator

bors commented Dec 21, 2021

☀️ Try build successful - checks-actions
Build commit: 2214d3e77bea8be80a245351159c1781a52d7f71 (2214d3e77bea8be80a245351159c1781a52d7f71)

@rust-timer
Copy link
Collaborator

Queued 2214d3e77bea8be80a245351159c1781a52d7f71 with parent e100ec5, future comparison URL.

@petrochenkov
Copy link
Contributor

r? @michaelwoerister

@rust-timer
Copy link
Collaborator

Finished benchmarking commit (2214d3e77bea8be80a245351159c1781a52d7f71): comparison url.

Summary: This benchmark run did not return any relevant changes.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR led to changes in compiler perf.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf -perf-regression

@rustbot rustbot removed the S-waiting-on-perf Status: Waiting on a perf run to be completed. label Dec 22, 2021
@michaelwoerister
Copy link
Member

LGTM, thanks @Aaron1011!

@bors r+

@bors
Copy link
Collaborator

bors commented Jan 3, 2022

📌 Commit f1d6823 has been approved by michaelwoerister

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jan 3, 2022
@bors
Copy link
Collaborator

bors commented Jan 3, 2022

⌛ Testing commit f1d6823 with merge b5efe57...

@bors
Copy link
Collaborator

bors commented Jan 3, 2022

☀️ Test successful - checks-actions
Approved by: michaelwoerister
Pushing b5efe57 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jan 3, 2022
@bors bors merged commit b5efe57 into rust-lang:master Jan 3, 2022
@rustbot rustbot added this to the 1.59.0 milestone Jan 3, 2022
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (b5efe57): comparison url.

Summary: This benchmark run did not return any relevant changes.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants