Bazel does not terminate subprocesses on ^C on windows #10573
Assignees
Labels
area-Windows
Windows-specific issues and feature requests
P2
We'll consider working on this in future. (Assignee optional)
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
type: bug
Comments
meteorcloudy
added
P2
|
/cc @laszlocsomor |
|
I can repro when running Bazel from MSYS, but not when running from cmd.exe |
|
bazel is launched from an msys2 shell, though the shell itself is launched from a nested combination of msys2 bash scripts & .bat files executed by Are you saying that things should work better if I do |
|
I mean if you run Thanks for the clarification, I'll investigate more. |
|
This seems to be an ancient MSYS2/MingW bug. Apparently they terminate programs on Ctrl+C instead of allowing them to handle the signal: https://stackoverflow.com/a/52657873/7778502 Open
This is why Ctrl+C will terminate the client and its children, but not the server nor the server's children (which One workaround people suggest is to run Bazel under Another workaround is to use Or run Bazel from cmd.exe, everything works nicely there, even in |
|
Summary: we can't fix this bug. |
meteorcloudy
pushed a commit
to meteorcloudy/bazel
that referenced
this issue
Feb 10, 2020
Baseline: 9807e50 Cherry picks: + 217c918: Swith to meteorcloudy/bazel + 16b89e2: Remove git notes from release process + 97869c1: Add blabla2 Incompatible changes: - The following attributes of CcToolchainProvider, which formerly were accessible both as fields (x.f) and as methods (x.f()), are now only fields: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 New features: - Similar to the [.bazelignore](https://docs.bazel.build/versions/master/guide.html #.bazelignore) in the main repository, a `.bazelignore` file in external repository will cause the specified directories to be ignored by Bazel. Bazel won't try to identify any packages under the directories, but the files can still be referenced in other BUILD files. - bazelignore files now support line comments, e.g. "# this is a comment" Important changes: - Experimental support for d8 merger is now available for use using --define=android_dexmerger_tool=d8_dexmerger. - Critical path run time should not have a longer run time than total execution run time. - Remove "please do not import" warning for cc rules. - x.f() is now equivalent to y=x.f; y(). That is, x.f should return the same attribute value regardless of whether it is accessed as a field or called like a method. Any arguments to the call are evaluated after the x.f operation. - Add desugaring support for RoleManager#addRoleHolderAsUser - Adds ctx.target_platform_has_constraint to allow rules to check the target platform's constraints. - Critical path run time should not have a longer run time than total execution run time. - Post new ConvenienceSymlinksIdentifiedEvent to the BuildEventProtocol when --experimental_convenience_symlinks_bep_event is enabled. - Keyword-only arguments are now allowed: def foo(a, *, k): pass def foo(a, *b, k): pass where k can be specified only by keyword: foo(5, k=6) - Generated Go protobufs now depend on //net/proto2/go:protodeps in addition to //net/proto2/go:proto - cquery 'somepath' returns more reliable results when the dep has a different configuration than the parent. To get a result for `somepath(//foo, //bar`) where //bar isn't in the top-level configuration, run your query with `--universe_scope=//foo`. See cquery docs for details. - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (bazelbuild#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Alex Kirchhoff, aman, Andreas Herrmann, Benjamin Peterson, Benjamin Peterson, Bor Kae Hwang, Brian Silverman, David Ostrovsky, Elliotte Rusty Harold, Emran BatmanGhelich, George Gensure, Greg Estren, Jeff Palm, John Millikin, Jonathan Beverly, Mark Nevill, Michael McLoughlin, nikola-sh, Nikolay Shelukhin, Patrick Niklaus, Peter, Philipp Wollermann, Ryan Beasley, Shin Yamamoto, Yannic Bonenberger, Yannic, Yen-Chi Chen.
meteorcloudy
pushed a commit
to meteorcloudy/bazel
that referenced
this issue
Feb 10, 2020
Baseline: ef34fe6 Cherry picks: + 3983e21: Swith to meteorcloudy/bazel + 2c16f0dc3dc62d2e567ffa5bb34d3ffdd99a8b57: Remove git notes from release process + 08743313e709e8d1d590fa471ef1ca97a5a84d19: Add blabla2 Incompatible changes: - The following attributes of CcToolchainProvider, which formerly were accessible both as fields (x.f) and as methods (x.f()), are now only fields: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 New features: - Similar to the [.bazelignore](https://docs.bazel.build/versions/master/guide.html #.bazelignore) in the main repository, a `.bazelignore` file in external repository will cause the specified directories to be ignored by Bazel. Bazel won't try to identify any packages under the directories, but the files can still be referenced in other BUILD files. - bazelignore files now support line comments, e.g. "# this is a comment" Important changes: - Experimental support for d8 merger is now available for use using --define=android_dexmerger_tool=d8_dexmerger. - Critical path run time should not have a longer run time than total execution run time. - Remove "please do not import" warning for cc rules. - x.f() is now equivalent to y=x.f; y(). That is, x.f should return the same attribute value regardless of whether it is accessed as a field or called like a method. Any arguments to the call are evaluated after the x.f operation. - Add desugaring support for RoleManager#addRoleHolderAsUser - Adds ctx.target_platform_has_constraint to allow rules to check the target platform's constraints. - Critical path run time should not have a longer run time than total execution run time. - Post new ConvenienceSymlinksIdentifiedEvent to the BuildEventProtocol when --experimental_convenience_symlinks_bep_event is enabled. - Keyword-only arguments are now allowed: def foo(a, *, k): pass def foo(a, *b, k): pass where k can be specified only by keyword: foo(5, k=6) - Generated Go protobufs now depend on //net/proto2/go:protodeps in addition to //net/proto2/go:proto - cquery 'somepath' returns more reliable results when the dep has a different configuration than the parent. To get a result for `somepath(//foo, //bar`) where //bar isn't in the top-level configuration, run your query with `--universe_scope=//foo`. See cquery docs for details. - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (bazelbuild#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Alex Kirchhoff, aman, Andreas Herrmann, Benjamin Peterson, Benjamin Peterson, Bor Kae Hwang, Brian Silverman, David Ostrovsky, Elliotte Rusty Harold, Emran BatmanGhelich, George Gensure, Greg Estren, Jeff Palm, John Millikin, Jonathan Beverly, Mark Nevill, Michael McLoughlin, nikola-sh, Nikolay Shelukhin, Patrick Niklaus, Peter, Philipp Wollermann, Ryan Beasley, Shin Yamamoto, Yannic Bonenberger, Yannic, Yen-Chi Chen.
meteorcloudy
pushed a commit
to meteorcloudy/bazel
that referenced
this issue
Feb 10, 2020
Baseline: 9807e50 Cherry picks: + 3983e21: Swith to meteorcloudy/bazel + 8d29820: Remove git notes from release process + 3e83ee1: Add blabla2 Incompatible changes: - The following attributes of CcToolchainProvider, which formerly were accessible both as fields (x.f) and as methods (x.f()), are now only fields: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 New features: - Similar to the [.bazelignore](https://docs.bazel.build/versions/master/guide.html #.bazelignore) in the main repository, a `.bazelignore` file in external repository will cause the specified directories to be ignored by Bazel. Bazel won't try to identify any packages under the directories, but the files can still be referenced in other BUILD files. - bazelignore files now support line comments, e.g. "# this is a comment" Important changes: - Experimental support for d8 merger is now available for use using --define=android_dexmerger_tool=d8_dexmerger. - Critical path run time should not have a longer run time than total execution run time. - Remove "please do not import" warning for cc rules. - x.f() is now equivalent to y=x.f; y(). That is, x.f should return the same attribute value regardless of whether it is accessed as a field or called like a method. Any arguments to the call are evaluated after the x.f operation. - Add desugaring support for RoleManager#addRoleHolderAsUser - Adds ctx.target_platform_has_constraint to allow rules to check the target platform's constraints. - Critical path run time should not have a longer run time than total execution run time. - Post new ConvenienceSymlinksIdentifiedEvent to the BuildEventProtocol when --experimental_convenience_symlinks_bep_event is enabled. - Keyword-only arguments are now allowed: def foo(a, *, k): pass def foo(a, *b, k): pass where k can be specified only by keyword: foo(5, k=6) - Generated Go protobufs now depend on //net/proto2/go:protodeps in addition to //net/proto2/go:proto - cquery 'somepath' returns more reliable results when the dep has a different configuration than the parent. To get a result for `somepath(//foo, //bar`) where //bar isn't in the top-level configuration, run your query with `--universe_scope=//foo`. See cquery docs for details. - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (bazelbuild#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Alex Kirchhoff, aman, Andreas Herrmann, Benjamin Peterson, Benjamin Peterson, Bor Kae Hwang, Brian Silverman, David Ostrovsky, Elliotte Rusty Harold, Emran BatmanGhelich, George Gensure, Greg Estren, Jeff Palm, John Millikin, Jonathan Beverly, Mark Nevill, Michael McLoughlin, nikola-sh, Nikolay Shelukhin, Patrick Niklaus, Peter, Philipp Wollermann, Ryan Beasley, Shin Yamamoto, Yannic Bonenberger, Yannic, Yen-Chi Chen.
meteorcloudy
pushed a commit
to meteorcloudy/bazel
that referenced
this issue
Feb 10, 2020
Baseline: 9807e50 Cherry picks: + 3983e21: Swith to meteorcloudy/bazel + a9d2d07: Remove git notes from release process + 8c1b17b: Add blabla2 Incompatible changes: - The following attributes of CcToolchainProvider, which formerly were accessible both as fields (x.f) and as methods (x.f()), are now only fields: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 New features: - Similar to the [.bazelignore](https://docs.bazel.build/versions/master/guide.html #.bazelignore) in the main repository, a `.bazelignore` file in external repository will cause the specified directories to be ignored by Bazel. Bazel won't try to identify any packages under the directories, but the files can still be referenced in other BUILD files. - bazelignore files now support line comments, e.g. "# this is a comment" Important changes: - Experimental support for d8 merger is now available for use using --define=android_dexmerger_tool=d8_dexmerger. - Critical path run time should not have a longer run time than total execution run time. - Remove "please do not import" warning for cc rules. - x.f() is now equivalent to y=x.f; y(). That is, x.f should return the same attribute value regardless of whether it is accessed as a field or called like a method. Any arguments to the call are evaluated after the x.f operation. - Add desugaring support for RoleManager#addRoleHolderAsUser - Adds ctx.target_platform_has_constraint to allow rules to check the target platform's constraints. - Critical path run time should not have a longer run time than total execution run time. - Post new ConvenienceSymlinksIdentifiedEvent to the BuildEventProtocol when --experimental_convenience_symlinks_bep_event is enabled. - Keyword-only arguments are now allowed: def foo(a, *, k): pass def foo(a, *b, k): pass where k can be specified only by keyword: foo(5, k=6) - Generated Go protobufs now depend on //net/proto2/go:protodeps in addition to //net/proto2/go:proto - cquery 'somepath' returns more reliable results when the dep has a different configuration than the parent. To get a result for `somepath(//foo, //bar`) where //bar isn't in the top-level configuration, run your query with `--universe_scope=//foo`. See cquery docs for details. - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (bazelbuild#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Alex Kirchhoff, aman, Andreas Herrmann, Benjamin Peterson, Benjamin Peterson, Bor Kae Hwang, Brian Silverman, David Ostrovsky, Elliotte Rusty Harold, Emran BatmanGhelich, George Gensure, Greg Estren, Jeff Palm, John Millikin, Jonathan Beverly, Mark Nevill, Michael McLoughlin, nikola-sh, Nikolay Shelukhin, Patrick Niklaus, Peter, Philipp Wollermann, Ryan Beasley, Shin Yamamoto, Yannic Bonenberger, Yannic, Yen-Chi Chen.
|
Is it known if the bug applies to both MSYS and WSL? If WSL is also affected is it Ok to have it installed as long as the actual build is run from CMD.EXE? Because it is really hard to design Windows build without relying on WSL. |
|
@konste We never tested Bazel on Windows with WSL. Are you using Bazel with WSL? If so, can you try to reproduce this issue in WSL? |
|
I have WSL (Ubuntu) and MSYS2 installed. Using windows bash works fine (Ctrl-C stops the bazel server correctly) I am using Bazel 2.1.0 on Windows 10 |
|
@tdm20 That's great to hear! Thank you! |
bazel-io
pushed a commit
that referenced
this issue
Mar 3, 2020
Baseline: 78055ef Incompatible changes: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 Important changes: - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - The --starlark_cpu_profile=<file> flag writes a profile in pprof format containing a statistical summary of CPU usage by all Starlark execution during the bazel command. Use it to identify slow Starlark functions in loading and analysis. - --ram_utilization_factor will be deprecated. Please use --local_ram_resources=HOST_RAM*<float> - Docs: glob() documentation is rewritten, and now it points out a pitfall of rules shadowing glob-matched files. This release contains contributions from many people at Google, as well as Alessandro Patti, Alex Kirchhoff, aman, Artur Dryomov, Benjamin Peterson, Benjamin Peterson, David Ostrovsky, Elliotte Rusty Harold, Eric Klein, George Chiramel, George Gensure, Guillaume Bouchard, Hui-Zhi, John Millikin, Jonathan Springer, Laurent Le Brun, Michael McLoughlin, nikola-sh, Nikolaus Wittenstein, Nikolay Shelukhin, Yannic Bonenberger, Yannic.
AlessandroPatti
pushed a commit
to uber-common/bazel
that referenced
this issue
Mar 3, 2020
Baseline: 78055ef Incompatible changes: - The --[no]incompatible_windows_bashless_run_command flag is no longer supported. It was flipped in Bazel 1.0 - The --[no]incompatible_windows_native_test_wrapper flag is no longer supported. It was flipped in Bazel 1.0 Important changes: - Consistent target naming style in example target names. - cquery's config() now supports arbitrary configurations. - The flag --incompatible_disallow_dict_lookup_unhashable_keys is removed. - Include target label in Python version error message. - The flag --incompatible_remap_main_repo is removed. - Windows: we now discourage running Bazel from MSYS2 because of a newly found bug (bazelbuild#10573) - Reduced the packaging time (`package-bazel.sh`) for the `//src:bazel-dev` Bazel development build target from 14s to 6s. Use `//src:bazel-dev` if you're iterating rapidly on a local Bazel changes, and use `//src:bazel --compilation_mode=opt` for release builds. - cquery: "//foo:bar" now means "all configured targets with label //foo:bar" instead of "choose an arbitrary configured target with label //foo:bar". See cquery docs for details. - WORKSPACE and BUILD.bazel files of http_archive repositories can now be patched using the "patch_cmds" and "patches" attributes. - Actions with "parse" on the critical path should no longer finish in the future. - Flags that affect external repositories like "--override_repository" can now be addressed in bazelrc files using the "common" command, without causing commands like "bazel shutdown" to fail. - The flag --incompatible_disallow_unverified_http_downloads is removed. - Create the incompatibleApplicableLicenses flag. We plan to flip this from false to true in Bazel 4.x. Implementation to follow. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - Treat .cu and .cl files as C++ source. CUDA or OpenCL are not natively supported and will require custom flags to compile with e.g. clang. - The --starlark_cpu_profile=<file> flag writes a profile in pprof format containing a statistical summary of CPU usage by all Starlark execution during the bazel command. Use it to identify slow Starlark functions in loading and analysis. - --ram_utilization_factor will be deprecated. Please use --local_ram_resources=HOST_RAM*<float> - Docs: glob() documentation is rewritten, and now it points out a pitfall of rules shadowing glob-matched files. This release contains contributions from many people at Google, as well as Alessandro Patti, Alex Kirchhoff, aman, Artur Dryomov, Benjamin Peterson, Benjamin Peterson, David Ostrovsky, Elliotte Rusty Harold, Eric Klein, George Chiramel, George Gensure, Guillaume Bouchard, Hui-Zhi, John Millikin, Jonathan Springer, Laurent Le Brun, Michael McLoughlin, nikola-sh, Nikolaus Wittenstein, Nikolay Shelukhin, Yannic Bonenberger, Yannic.
philwo
added
the
team-OSS
|
I've just installed Bazel using Scoop, and then
Nevertheless, there are other strange things happening. Bazel (attempting to build |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
Bazel does not terminate subprocesses on ^C on windows.
When interrupted with ^C the already launched commands continue to run.
If subsequent execution of bazel needs to restart the server, it will silently hang until the old commands have finished.
If one of the old commands is manually killed, then all remaining commands appear to be killed/cleaned up right away.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Reproduction:
Bazel is interrupted here and we're back on the console.
The action continues to run in the background and keeps appending lines to
foo:What operating system are you running Bazel on?
Windows Server 1809
What's the output of
bazel info release?release 2.0.0
Have you found anything relevant by searching the web?
No. Discussed w/ @meteorcloudy who suggested filing a bug.
The text was updated successfully, but these errors were encountered: