-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Add debugging flag to assert state of incremental cache #85864
Copy link
Copy link
Closed
Labels
A-incr-compArea: Incremental compilationArea: Incremental compilationA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Metadata
Metadata
Assignees
Labels
A-incr-compArea: Incremental compilationArea: Incremental compilationA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Type
Fields
Give feedbackNo fields configured for issues without a type.
In PR #85702, I added a test that relies on the incremental cache still being saved if a linker error occurs. It would be good for the test to assert that this assumption is actually true. We could add a new flag
-Z assert-incr-state=<state>, where<state>can be:none- we didn't find any previous session dirs whatsoevermismatch- we found an existing session dir, but did not load it to do a command-line arg hash mismatch.loaded- we found and loaded an existing session dir. Note that this says nothing about whether any particular query will be found to be red or green.