-
Notifications
You must be signed in to change notification settings - Fork 2k
Remove cancellation workflow, fail-fast. #1415
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
@nathanhammond is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
99abc18
to
13e0e6d
Compare
Sounds good to me. |
@@ -96,7 +102,7 @@ jobs: | |||
uses: actions/setup-node@v2 | |||
with: | |||
node-version: 16 | |||
cache: pnpm | |||
cache: ${{matrix.manager}} |
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 was getting pretty annoying yesterday, thanks for the fix!
Looks like the test failures might be related? They appear to be due to package-manager and caching stuff. |
A flaky test can bring down an entire set of CI runs but I only notice when I go back to look at the results, which means I've already waited for what I instinctively feel is the entire duration of the tests. Cancelled runs give me no information about the change.
Like this run here:
https://github.com/vercel/turborepo/runs/6934131393?check_suite_focus=true
I only wanted to make sure it passed Windows CI, but that got cancelled for reason of a flaky test on Linux.
This removes our cancellation workflow (replaced by built-in
concurrency
groups), and disables fast fail.It also corrects a bug in caching.