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

Flip --incompatible_windows_escape_python_args #8478

Closed

Conversation

laszlocsomor
Copy link
Contributor

CI test results (Bazel@HEAD + Downstream):
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1003

The flag affects Windows only, and on Windows only
two projects are broken: rules_foreign_cc and
rules_nodejs.

These are also broken on other platforms, and in
the previous build:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1002

Therefore I'm reasonably sure they are not broken
by this PR. That said, we can't completely be
sure because the tests didn't run.

See #7974

Change-Id: I2cc09a4e9295495062dc4ac79b859dec6512b1b7

CI test results (Bazel@HEAD + Downstream):
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1003

The flag affects Windows only, and on Windows only
two projects are broken: rules_foreign_cc and
rules_nodejs.

These are also broken on other platforms, and in
the previous build:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1002

Therefore I'm reasonably sure they are not broken
by this PR. That said, we can't completely be
sure because the tests didn't run.

See bazelbuild#7974

Change-Id: I2cc09a4e9295495062dc4ac79b859dec6512b1b7
@laszlocsomor laszlocsomor requested a review from hlopko as a code owner May 28, 2019 14:23
@laszlocsomor laszlocsomor requested review from meteorcloudy and brandjon and removed request for hlopko May 28, 2019 14:23
@laszlocsomor
Copy link
Contributor Author

Thanks @meteorcloudy ! Also waiting for @brandjon to LGTM.

@bazel-io bazel-io closed this in a7af7c3 May 29, 2019
irengrig pushed a commit to irengrig/bazel that referenced this pull request Jun 18, 2019
CI test results (Bazel@HEAD + Downstream):
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1003

The flag affects Windows only, and on Windows only
two projects are broken: rules_foreign_cc and
rules_nodejs.

These are also broken on other platforms, and in
the previous build:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1002

Therefore I'm reasonably sure they are not broken
by this PR. That said, we can't completely be
sure because the tests didn't run.

See bazelbuild#7974

Change-Id: I2cc09a4e9295495062dc4ac79b859dec6512b1b7

Closes bazelbuild#8478.

Change-Id: I2cc09a4e9295495062dc4ac79b859dec6512b1b7
PiperOrigin-RevId: 250437116
irengrig pushed a commit to irengrig/bazel that referenced this pull request Jul 15, 2019
CI test results (Bazel@HEAD + Downstream):
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1003

The flag affects Windows only, and on Windows only
two projects are broken: rules_foreign_cc and
rules_nodejs.

These are also broken on other platforms, and in
the previous build:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1002

Therefore I'm reasonably sure they are not broken
by this PR. That said, we can't completely be
sure because the tests didn't run.

See bazelbuild#7974

Change-Id: I2cc09a4e9295495062dc4ac79b859dec6512b1b7

Closes bazelbuild#8478.

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

Successfully merging this pull request may close these issues.

4 participants