Skip to content
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

linker on windows sees truncated bazel-~1 paths #1963

Closed
alexeagle opened this issue Jun 16, 2020 · 2 comments
Closed

linker on windows sees truncated bazel-~1 paths #1963

alexeagle opened this issue Jun 16, 2020 · 2 comments
Labels
Can Close? We will close this in 30 days if there is no further activity

Comments

@alexeagle
Copy link
Collaborator

When merging #1440 I saw paths like
c:/b/ojvxx6nx/execroot/build_~1/bazel-~1/x64_wi~1/bin/internal/npm_in~1/test
in the bazel run tests like https://github.com/bazelbuild/rules_nodejs/blob/7d070ffadf9c3b41711382a4737b995f987c14fa/.bazelci/presubmit.yml#L12

Here's a repro showing the failure:
#1962

for now I extended the regex for bazel-out as a workaround

@github-actions
Copy link

github-actions bot commented Sep 8, 2020

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs in two weeks. Collaborators can add a "cleanup" or "need: discussion" label to keep it open indefinitely. Thanks for your contributions to rules_nodejs!

@github-actions github-actions bot added the Can Close? We will close this in 30 days if there is no further activity label Sep 8, 2020
@github-actions
Copy link

This issue was automatically closed because it went two weeks without a reply since it was labeled "Can Close?"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can Close? We will close this in 30 days if there is no further activity
Projects
None yet
Development

No branches or pull requests

1 participant