-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
ibazel cmd on Windows / update ibazel #16405
Comments
devversion
added a commit
to devversion/material2
that referenced
this issue
Jul 4, 2019
Updates `ibazel` to the latest version. This version comes with long awaited windows support that is now also usable in the components repository (based on manual testing). In follow-ups we should work towards switching away from `gulp test` to `ibazel`. Though we need to ensure that common workflows like debugging are still possible. Fixes angular#16405
jelbourn
pushed a commit
that referenced
this issue
Jul 9, 2019
Updates `ibazel` to the latest version. This version comes with long awaited windows support that is now also usable in the components repository (based on manual testing). In follow-ups we should work towards switching away from `gulp test` to `ibazel`. Though we need to ensure that common workflows like debugging are still possible. Fixes #16405
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
When I run any
yarn ibazel
command it fails and displays:What is the expected behavior?
To run bazel command specified as persistent process.
What is the current behavior?
FATAL ERROR message is displayed.
Environment
components-srcs:8.0.0-rc.1
Seems related:
bazelbuild/bazel-watcher#144
The text was updated successfully, but these errors were encountered: