Add a workaround for sigwait returning 0 but not setting the signal number.#2132
Open
copybara-service[bot] wants to merge 1 commit into
Open
Add a workaround for sigwait returning 0 but not setting the signal number.#2132copybara-service[bot] wants to merge 1 commit into
copybara-service[bot] wants to merge 1 commit into
Conversation
copybara-service
Bot
force-pushed
the
cl/948545330
branch
from
5e6e0f7 to
4dc25e9
Compare
…umber. This should never happen, but I've seen it in recent MacOS CI runs. It does not break the fuzzing engine, but may cause unnecessary cleanup timeout. PiperOrigin-RevId: 948545330
copybara-service
Bot
force-pushed
the
cl/948545330
branch
from
4dc25e9 to
9d7cd38
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a workaround for sigwait returning 0 but not setting the signal number.
This should never happen, but I've seen it in recent MacOS CI runs.
It does not break the fuzzing engine, but may cause unnecessary cleanup timeout.