-
Notifications
You must be signed in to change notification settings - Fork 23
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
Run tests in parallel #378
Conversation
edfc757
to
0f6cedc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Every little bit helps! See my question inline though, we might be missing a t.Parallel
call here still unless I'm missing something.
@@ -107,9 +107,6 @@ func TestPulumiTemplateTests(t *testing.T) { | |||
for _, test := range testCases { | |||
test := test | |||
t.Run(test.template, func(t *testing.T) { | |||
// TODO: Not running these in parallel to help with disk space. | |||
// https://github.com/pulumi/pulumi-docker-containers/issues/215 | |||
// t.Parallel() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're removing the TODO here, but not enabling running in parallel 🤔 was this an oversight or intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm a little weird, we use program test below, which calls t.Parallel().
I updated this now so that we call t.Parallel() ourselves, and tell program test not to. This way the pulumi new
command should be part of the parallel execution too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I had missed that. ProgramTest calling parallel itself always trips me up.
0f6cedc
to
219e3f9
Compare
This doesn't gain us that much, the slowest image, provider-build-environment, seems to go from 38 to 35 minutes.