-
Notifications
You must be signed in to change notification settings - Fork 204
Run tests in parallel for pkg/app/piped #3383
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
Conversation
pipecd-bot
left a comment
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.
pipecd-bot
left a comment
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.
|
The golinter build is completed with FAILURE. The build will be triggered again when you push any other commits. Or you can trigger it manually by You can check the build log from here. |
pipecd-bot
left a comment
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.
This comment was marked as duplicate.
This comment was marked as duplicate.
|
/close |
|
@Hosshii: Closed this pull request in response to this comment. |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
This is more faster than others (add t.parallel to all test and add t.parallel to slow test). |
knanao
left a comment
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.
Nice catch!
Let me check one point.
If we run cases of table driven tests sequentially, the tests will be extremely slow?
|
I think If each case of the table is slow, parallelization would speed it up. Otherwise, the cost of parallelization would be more expensive. |
|
I wrote these tests before #3370 (comment). So these tests uses |
|
Thanks.
That's why, let us apply this! |
|
Thank you! I removed sub-level t.parallel |
|
Awesome! |
|
Here you go 🙌 |
What this PR does / why we need it:
Add
t.Parallelto execute tests in parallel. And delete unused test files.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: