-
Notifications
You must be signed in to change notification settings - Fork 522
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
ts_library does not work with Bazel 1.0.0+ on Windows #1307
Comments
Looks flaky. I saw it only once on initial build after clone and can't reproduce a 2nd time. |
Characterized this some more. Its not a worker problem. Something with
|
Ok. Figured it out and I have a repro on rules_nodejs and a fix. When running Relevant code in the bazel repo is:
In rules_nodejs I was able to repo this with bazel 1.0.0 & 1.1.0 in the bazel-in-bazel tests only as ts_library targets in the root repo don't meet the external runfiles files only case. https://buildkite.com/bazel/rules-nodejs-nodejs/builds/4678#1e469c69-7e89-4066-a2c2-0dbb0e8a48e5 && https://buildkite.com/bazel/rules-nodejs-nodejs/builds/4679#093fd1ba-1d6b-40ac-be71-ef8869c4eb34:
|
Fix is a one-liner in the loader |
This fixes a new issue introduced with Bazel 1.0.0 where Bazel adds a `{workspace}/.runfile` to the runfiles MANIFEST and this messes with the node_loader resolve logic on Windows.
This fixes a new issue introduced with Bazel 1.0.0 where Bazel adds a `{workspace}/.runfile` to the runfiles MANIFEST and this messes with the node_loader resolve logic on Windows.
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307.
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307.
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307. PR Close #33458
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307. PR Close angular#33458
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307. PR Close angular#33458
Pre-req for updating repo, integration & @bazel/schematics to Bazel 1.0.0 as this release brings in a fix for ts_library on Windows with Bazel 1.0.0+. See bazel-contrib/rules_nodejs#1307. PR Close angular#33458
Updating to Bazel 1.0.0 on Windows ts_library fails with
Originally seen on angular WIndows CI after angular/angular#33367 landed: https://app.circleci.com/jobs/github/angular/angular/501770
I can repro on my local Windows machine.
/cc @josephperrott @alexeagle
This is blocking the Angular update to Bazel 1.0.0
The text was updated successfully, but these errors were encountered: