Connect to Chrome via pipe rather than WebSocket #259
Merged
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.
Recently we met flaky test results again.
This PR sets
puppeteer.launch({ pipe: true })
to get more reliability of connection to Chrome by Puppeteer.pipe: true
makes connection to Chrome process through process pipe instead of WebSocket, so we could expect decrease of flaky test results caused by unstable network on GitHub Actions environment.