Repository navigation
Conversation
On the hosted macos-15 runner the first TestSimulatorProcessResults case took 3m32s in one run and 9m56s in another on the same image (20261104.0514.1). The three cases share one go test process, so go test's default ten-minute limit ended the run four seconds into simulatorplain, and every PR's apple-simulator job has been failing that way since about 00:00Z on 2026-11-18. The package now gets 25 minutes and the job 40.
houko
force-pushed
the
ci/simulator-timeout
branch
from
November 18, 2026 02:49
b1f5694 to
297c00b
Compare
This was referenced Nov 18, 2026
This branch has not been deployed
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
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.
Every PR's
apple-simulatorjob has been failing since about 00:00Z today, for example on #631:This isn't a code regression. Main's last green run (26451ed) and its first red one (4637dda) differ only by one line of docs/architecture/tool.md. Both runs used the same hosted image, macos-15-arm64 20261104.0514.1. The difference is how long the simulator boots: the first case took 3m32s in the green run and 9m56s in the red one. All three cases run in one go test process, so go test's default ten-minute limit kills the process a few seconds into the second case.
Change
TestSimulatorProcessResultsgets-- -timeout=25m, the same way the gallery step got its limit in ci: give the Test step's packages twenty minutes #558. The flag is forwarded to go test: on the Linux build host,-- -timeout=1nsmakes the run fail at once.timeout-minutesgoes from 20 to 40, so the job limit stays above the package limit.Not changed
Why the simulator boot is sometimes slow on hosted runners. This PR gives that variance enough headroom; it doesn't make the boot faster.