chore(ci): run noir tests in parallel to building e2e tests #9977
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.
I think it's worth running these two tests in parallel with building the main e2e images.
From what I remember, the justification why we gate everything based on
build
is to avoid having N different jobs fighting over building various earthly targets slowing everything down:noir-test
: This doesn't share any steps pastbuild-images
except for+nargo-src
so it's almost entirely separate to the mainbuild
step.noir-format
: This job shares the+nargo
and thenoir-projects+source
steps which are both very early in the pipeline. I think the benefit of flagging up potential formatting issues 20mins earlier is worth the small amount of overlap.That said
noir-projects+source
currently relies on a bb build which is very odd. I'd want to move that to a later step in order to avoid depending on bb.