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

blaze_util_posix: handle killpg failures #18299

Closed

Conversation

sluongng
Copy link
Contributor

@sluongng sluongng commented May 3, 2023

In case Bazel JVM server is stuck, it would be useful to know whether
the SIGKILL was sent successfully or not.

If not, log out the error message from errno.

@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label May 3, 2023
@Pavank1992 Pavank1992 added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label May 3, 2023
In case Bazel JVM server is stuck, it would be useful to know whether
the SIGKILL was sent successfully or not.

If not, log out the error message from errno.
@sluongng
Copy link
Contributor Author

sluongng commented May 8, 2023

The CI is failing due to an unrelated issue with //src/test/shell/bazel:bazel_sandboxing_networking_test that could be reproduced on master.

I think this PR is ready for review.

@meteorcloudy meteorcloudy added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels May 9, 2023
@copybara-service copybara-service bot closed this in 09e3a81 May 9, 2023
@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label May 9, 2023
@sluongng
Copy link
Contributor Author

sluongng commented May 9, 2023

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label May 9, 2023
@keertk
Copy link
Member

keertk commented May 9, 2023

@bazel-io fork 6.3.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label May 9, 2023
iancha1992 pushed a commit that referenced this pull request May 17, 2023
In case Bazel JVM server is stuck, it would be useful to know whether
the SIGKILL was sent successfully or not.

If not, log out the error message from errno.

Closes #18299.

PiperOrigin-RevId: 530615358
Change-Id: I4ddf9996ce80520ff19c306fe95429550e931a8b

Co-authored-by: Son Luong Ngoc <sluongng@gmail.com>
fweikert pushed a commit to fweikert/bazel that referenced this pull request May 25, 2023
In case Bazel JVM server is stuck, it would be useful to know whether
the SIGKILL was sent successfully or not.

If not, log out the error message from errno.

Closes bazelbuild#18299.

PiperOrigin-RevId: 530615358
Change-Id: I4ddf9996ce80520ff19c306fe95429550e931a8b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants