-
Notifications
You must be signed in to change notification settings - Fork 294
[Merged by Bors] - feat(ci): run lint and tests in parallel #2736
Conversation
|
|
Apparently the zip file doesn't preserve the permissions. We probably need to switch to "precompiled tar.gz". |
Yeah, that looks like it's tracked here: actions/upload-artifact#38 |
Done.
I don't understand. Isn't that the step that generates and uploads the artifact?
Done. |
bors try |
tryBuild succeeded: |
651d29f
to
9e31f1e
Compare
bors r+ |
Actions doesn't let us run *steps* in parallel, but we can run *jobs* in parallel. The lint and test jobs are part of the same *workflow*. Understanding Actions terminology is half the battle. Co-authored-by: Rob Lewis <[email protected]> Co-authored-by: Bryan Gin-ge Chen <[email protected]>
Pull request successfully merged into master. Build succeeded: |
Sorry, I missed that at first. I thought github actions has some built-in support to save the current directory. |
Actions doesn't let us run *steps* in parallel, but we can run *jobs* in parallel. The lint and test jobs are part of the same *workflow*. Understanding Actions terminology is half the battle. Co-authored-by: Rob Lewis <[email protected]> Co-authored-by: Bryan Gin-ge Chen <[email protected]>
Actions doesn't let us run *steps* in parallel, but we can run *jobs* in parallel. The lint and test jobs are part of the same *workflow*. Understanding Actions terminology is half the battle. Co-authored-by: Rob Lewis <[email protected]> Co-authored-by: Bryan Gin-ge Chen <[email protected]>
Actions doesn't let us run steps in parallel, but we can run jobs in parallel. The lint and test jobs are part of the same workflow. Understanding Actions terminology is half the battle.