-
Notifications
You must be signed in to change notification settings - Fork 524
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
test(builtin): add test for issue 1813 #1814
Conversation
d0e03c7
to
41ba541
Compare
f2099da
to
c997c99
Compare
Issue bazel-contrib#1813 was fixed by bazel-contrib#1800 which is already landed. bazel-contrib#1805 also fixes via a different mechanism and will also land soon.
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.
sweet
how did we not have patch-package in the postinstall? more patching FTW!
"--no-cache", | ||
"--no-watchman", | ||
"--ci", | ||
# On Windows, spawing workers is broken |
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.
oh! I wish I could use this to land the always-link-bins PR too
# On Windows, spawing workers is broken | ||
"--runInBand", | ||
"--config", | ||
"$$(rlocation $(rootpath jest.config.js))", |
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.
random note: any time we write this under the /examples
directory we should comment about it
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.
It would be rad if this were args=[".dist/bin/jest.config.js"])
and we fixed it up later in the toolchain
Issue #1813 was fixed by #1800 which is already landed. #1805 also fixes via a different mechanism and will also land soon.