Skip to content
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

Use cargo-chef for vm-monitor builds #991

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sharnoff
Copy link
Member

Before this PR, pg16-disk-test:
Clean build took 266s. Rebuilding from main+1 took 201s.

With this PR, pg16-disk-test:
Clean build took 303s. Rebuilding from main+1 took 101s.

(main+1 was jcsp/shard-split-logging; 75747cdbf -> 7f7f33f7e)

This is still quite a bit more time to rebuild than I'd like. The final step of building vm-monitor actually takes a surprisingly long time.

Also, there's this strange thing where the cargo chef image spends time installing clippy et al during prepare & cook (so, we actually end up doing it twice!). It doesn't take too long, but it's worth fixing that before merging, because there's no sense being wasteful.

Before this PR, pg16-disk-test:
Clean build took 266s. Rebuilding from main+1 took 201s.

With this PR, pg16-disk-test:
Clean build took 303s. Rebuilding from main+1 took 101s.

(main+1 was jcsp/shard-split-logging; 75747cdbf -> 7f7f33f7e)

This is still quite a bit more time to rebuild than I'd like. The final
step of building vm-monitor actually takes a surprisingly long time.

Also, there's this strange thing where the cargo chef image spends time
installing clippy et al during prepare & cook (so, we actually end up
doing it twice!). It doesn't take *too* long, but it's worth fixing that
before merging, because there's no sense being wasteful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant