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

[6.1.0] Allow the timeout value for execute calls on a mac to be set via an environment variable #17521

Conversation

keith
Copy link
Member

@keith keith commented Feb 16, 2023

In certain setups, these calls to xcrun during bazel setup have been reported to sometimes take more than 2 minutes (see
#17437). We have already bumped this timeout multiple times, which is currently 60 for some calls and 120 for others. Standardize the default timeout to 120, and allow the timeout to be override via BAZEL_OSX_EXECUTE_TIMEOUT, to allow individual enviroments to increase that even more if needed.

PiperOrigin-RevId: 510200188
Change-Id: I664eb7979c4fd2b46ccc87d073f319c1e6041d77

#17437

…nvironment variable

In certain setups, these calls to xcrun during bazel setup have been reported to
sometimes take more than 2 minutes (see
bazelbuild#17437).  We have already bumped this
timeout multiple times, which is currently 60 for some calls and 120 for others.
Standardize the default timeout to 120, and allow the timeout to be override via
BAZEL_OSX_EXECUTE_TIMEOUT, to allow individual enviroments to increase that even
more if needed.

PiperOrigin-RevId: 510200188
Change-Id: I664eb7979c4fd2b46ccc87d073f319c1e6041d77
@ShreeM01 ShreeM01 merged commit a60e201 into bazelbuild:release-6.1.0 Feb 16, 2023
@keith keith deleted the ks/allow-the-timeout-value-for-execute-calls-on-a-mac-to-be-set-via-an-environment-variable branch February 16, 2023 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants