fix(main): attempt to resolve macOS CI race condition#2
Closed
fix(main): attempt to resolve macOS CI race condition#2
Conversation
When running sequential PDF exports, macOS CI runners frequently throw a `SessionNotCreatedException` during driver creation. I noticed that subseqeunt tests run without issue. Hypothesis: The OS kernel requires additional time to release TCP ports and IPC locks from the previous headless Chrome instance before a new one can successfully bind. This commit attempts to fix the flakiness by introducing a 3-attempt retry loop with a 1-second delay in-between attempts.
thseiler
force-pushed
the
fix/add-chromesession-retry-mechanism
branch
from
54fbc5f to
3be5546
Compare
Owner
Author
|
was merged upstream, we can close this PR |
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.
When running sequential PDF exports, macOS CI runners frequently throw a
SessionNotCreatedExceptionduring driver creation. I noticed that subsequent tests run without issue.Hypothesis: The OS kernel requires additional time to release TCP ports and IPC locks from the previous headless Chrome instance before a new one can successfully bind.
This commit attempts to fix the flakiness by introducing a 3-attempt retry loop with a 1-second delay between attempts.
(This PR is created to trigger the CI in my forked repo)