[anneal][v2] Implement out-of-tree dependency chasing for expand command#3405
Open
mdittmer wants to merge 1 commit into
Open
[anneal][v2] Implement out-of-tree dependency chasing for expand command#3405mdittmer wants to merge 1 commit into
mdittmer wants to merge 1 commit into
Conversation
This was referenced May 25, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## Gnafivbpqcaatsvsxamgsjcudchscvaae #3405 +/- ##
==================================================================
Coverage 91.85% 91.85%
==================================================================
Files 20 20
Lines 6093 6093
==================================================================
Hits 5597 5597
Misses 496 496 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
mdittmer
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
17613f2 to
a3d47a3
Compare
mdittmer
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
e8af624 to
1c62cfd
Compare
mdittmer
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
a3d47a3 to
e60c407
Compare
mdittmer
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
43a1ef4 to
c7bc335
Compare
mdittmer
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
e60c407 to
56d3125
Compare
mdittmer
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
c7bc335 to
fafcee4
Compare
mdittmer
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
2 times, most recently
from
25f8010 to
d3b9547
Compare
mdittmer
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
0cf1bf4 to
964666d
Compare
mdittmer
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
d3b9547 to
491140c
Compare
This was referenced Jun 5, 2026
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
964666d to
c1eebe7
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
491140c to
a6368cf
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
a354b80 to
c6017c4
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
8ac1f77 to
89072a4
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
89072a4 to
69b654d
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
c6017c4 to
4b54759
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
4b54759 to
ec75210
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
69b654d to
4eb96b8
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
ec75210 to
8264851
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
4eb96b8 to
7439bf4
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
8264851 to
2de2f9c
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
7439bf4 to
0c5f2a0
Compare
This was referenced Jun 6, 2026
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
2de2f9c to
84850f1
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
0c5f2a0 to
4948425
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
4948425 to
8e2e362
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
84850f1 to
2c0a874
Compare
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
2c0a874 to
8b2c023
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
8e2e362 to
2a71cc0
Compare
Notes about largely unreviewed generated change: - Last test assertion looks dubious. Should probably switch all LLBC test verifications to something that properly parses the LLBC and makes more precise assertions. - Integration and structure requires more thought. It seems that only the scanner "knows" about this behaviour; is it being being plumbed through cmdline args and through run_charon? - New test (and probably other tests) should have their setup procedures overhauled/simplified. In general, I would expect the test to create a fixture, and then be able to pass largely static data to `run_charon()`, but right now it's manually setting up locked roots, etc., etc. gherrit-pr-id: Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
joshlf
force-pushed
the
Gnafivbpqcaatsvsxamgsjcudchscvaae
branch
from
8b2c023 to
c34277b
Compare
joshlf
force-pushed
the
Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3
branch
from
2a71cc0 to
bcd9f3e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Notes about largely unreviewed generated change:
Last test assertion looks dubious. Should probably switch all LLBC
test verifications to something that properly parses the LLBC and
makes more precise assertions.
Integration and structure requires more thought. It seems that only
the scanner "knows" about this behaviour; is it being being plumbed
through cmdline args and through run_charon?
New test (and probably other tests) should have their setup procedures
overhauled/simplified. In general, I would expect the test to create
a fixture, and then be able to pass largely static data to
run_charon(), but right now it's manually setting up locked roots,etc., etc.
Latest Update: v23 — Compare vs v22
📚 Full Patch History
Links show the diff between the row version and the column version.
⬇️ Download this PR
Branch
git fetch origin refs/heads/Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3 && git checkout -b pr-Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3 FETCH_HEADCheckout
git fetch origin refs/heads/Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3 && git checkout FETCH_HEADCherry Pick
git fetch origin refs/heads/Gxsjyiksx4pd6h5gzup7ensn4qtrxu6s3 && git cherry-pick FETCH_HEADPull
Stacked PRs enabled by GHerrit.