Too much recompilation when changing test targets #3732
Closed
Labels
Milestone
Comments
Sure, I can take a look at it. I should be able to find some time this week hopefully. |
Resolved via #3750, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this is a side-effect of the changes in #3565, implemented for #3483. CC @tswelsh. To repro, I created two packages,
foo
andbar
, withbar
depending onfoo
. I then ran the commands:Expected: the second command should do nothing, as all tests, libraries, and executables have already been run.
Actual: I saw the following output:
Notice how
foo
is unregistered, due to Stack thinking that the files changed. This occurs because the test suite and executable files are no longer included at all in the list of files in the package.Instead, we should track, for each package, the files needed on a per-component basis, and only rebuild based on this. This may tie in with @ezyang's work on per-component builds, not sure.
@tswelsh are you interested in taking a stab at this one?
The text was updated successfully, but these errors were encountered: