Open canstand opened 1 month ago
Looking at the recent commits, it always times out.
We see that the frameAttached
event for the main frame takes 5 seconds to arrive. This might be related to the slow-down to create a new process for the page.
We only see this happenning under the following circumstances:
History: Firefox was timing out on macos-14 since the test bots were introduced: https://github.com/microsoft/playwright/commit/4affcdef71624e9c0982f9eb5be19c7e4d2251ab
Reproduction:
Github Actions provide different architectures for the different size runners (details here and here):
macos-14
is aarch64 - ❌ has 5 seconds delay for each newPage
macos-14-large
is x86-64 - ✅ works as intendedmacos-14-xlarge
is aarch64 - ❌ has 5 seconds delay for each newPage
Locally, on my macbook with MacOS-14 and aarch64 - ✅ works as intended.
The easiest reproduction so far is just running the headless screenshot:
/Applications/Firefox.app/Contents/MacOS/firefox --headless --screenshot /tmp/foo.png about:blank
This seems to be an issue with Apple Silicon virtualization + Firefox.
Note: We temporarily mitigated it for now by continuing to use macOS Intel for our testing infrastructure in order to not loose any test coverage. In https://github.com/microsoft/playwright/pull/31121.
Note: this seems to be fixed with the latest Firefox Beta 128
Version
1.44.0
Steps to reproduce
Refer https://github.com/microsoft/playwright/actions/runs/8973892628
Jobs of firefox in macos-12(or macos-13) only took about 30m
(another proof: https://github.com/canstand/playwright-go/actions/runs/8999400053/job/24721476663 )
Expected behavior
The test job takes similar time under different macos versions.
Actual behavior
Test job in macos-14(firefox) timeout.
Additional context
No response
Environment