mirror of https://github.com/pulumi/pulumi.git
b357f25aa7
Currently we make running the tests depend on linting the program. This occasionally saves some GitHub actions runner time, when the lint step detects that the build is failing. However in many cases it's quite inconvenient, especially if the lint error is really just a lint error (e.g. because of a long line or something). In that case the submitter of the PR has to fix the lint first, and then push those changes, and wait for CI all over again, which can add a considerable amount of time (especially since CI is kinda slow, so at least I usually end up doing something else and checking back later). In addition it adds to the time it takes to run all tests in total, as the tests can't be run in parallel with linting (and linting takes more than a minute). Allow the tests to run in parallel instead. This means we can get the test results early, as long as the code builds fine. In some occasions that means some extra time spent on GitHub actions, but that's time well spent imo. |
||
|---|---|---|
| .. | ||
| ci-build-binaries.yml | ||
| ci-build-sdks.yml | ||
| ci-dev-release.yml | ||
| ci-info.yml | ||
| ci-lint.yml | ||
| ci-prepare-release.yml | ||
| ci-run-test.yml | ||
| ci-test-docs-generation.yml | ||
| ci.yml | ||
| command-dispatch.yml | ||
| cron-direct-build.yml | ||
| download-pulumi-cron.yml | ||
| on-community-pr.yml | ||
| on-merge.yml | ||
| on-pr-close.yml | ||
| on-pr-default.yml | ||
| on-pr.yml | ||
| on-push.yml | ||
| on-release.yml | ||
| pr-test-acceptance-on-dispatch.yml | ||
| pr-test-codegen-downstream.yml | ||
| pr-test-docs-gen-on-pr.yml | ||
| pr-test-docs-generation-on-dispatch.yml | ||
| rebase.yml | ||
| release-homebrew-tap.yml | ||
| release-pr.yml | ||
| release.pub | ||
| release.yml | ||
| sign.yml | ||
| trigger-homebrew-event.yml | ||
| trigger-release-docs-event.yml | ||