Skip to content

Use yarn mutex rather than cache-folder #359

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

Merged
merged 2 commits into from
Oct 5, 2018

Conversation

alexeagle
Copy link
Collaborator

This lets us reuse the downloaded artifact cache

This lets us reuse the downloaded artifact cache
@alexeagle alexeagle requested a review from Globegitter October 5, 2018 13:59
@alexeagle
Copy link
Collaborator Author

Probably fixes #358

Copy link
Collaborator

@gregmagolan gregmagolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool

@alexeagle alexeagle merged commit aafed6e into bazel-contrib:master Oct 5, 2018
@alexeagle alexeagle deleted the mutex branch October 5, 2018 16:34
alexeagle pushed a commit to alexeagle/rules_nodejs that referenced this pull request Oct 17, 2020
The typechecker is known to be slow to create due to microsoft/TypeScript#27997

By moving the non-typechecker checks earlier in the process, I was able to observe significant savings in the `perfTrace.wrap` total times:
- `CheckReturnValueRule`: 1,036ms, down from 2,102ms
- `MustUsePromisesRule`: 119ms, down from 1,174ms

Closes bazel-contrib#359

PiperOrigin-RevId: 225844645
alexeagle pushed a commit to alexeagle/rules_nodejs that referenced this pull request Oct 18, 2020
The typechecker is known to be slow to create due to microsoft/TypeScript#27997

By moving the non-typechecker checks earlier in the process, I was able to observe significant savings in the `perfTrace.wrap` total times:
- `CheckReturnValueRule`: 1,036ms, down from 2,102ms
- `MustUsePromisesRule`: 119ms, down from 1,174ms

Closes bazel-contrib#359

PiperOrigin-RevId: 225844645
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants