You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On current main (430e82c), Chromium 105.0.5195.102 and Linux, running xk6 run examples/device_emulation.js fails with:
ERRO[0030] navigating to "https://k6.io/": timed out after 30s
at reflect.methodValueCall (native)
at file:///home/ivan/Projects/grafana/xk6-browser/examples/device_emulation.js:17:30(40)
at native executor=per-vu-iterations scenario=default source=stacktrace
It doesn't happen all the time, but a good 90% on my machine, so it's fairly reproducible. @ankur22 was also able to reproduce it on macOS. Note that it doesn't happen in CI, since failed checks still exit the process with code 0, but I actually haven't seen it fail the check either.
We thought we addressed all navigation race conditions in #480, but apparently not, or this is a recent regression. 😞
The text was updated successfully, but these errors were encountered:
It doesn't have anything to do with device emulation itself. You can comment that out and not pass any options to browser.newContext(), and it would still time out.
It seems related to the site itself. E.g. this is the only example that loads https://k6.io/ instead of https://test.k6.io/. For test.k6.io, the test passes consistently.
On current
main
(430e82c), Chromium 105.0.5195.102 and Linux, runningxk6 run examples/device_emulation.js
fails with:The relevant stack trace is:
I.e. it's stuck waiting for the LifecycleEvent:
xk6-browser/common/frame_manager.go
Lines 671 to 675 in 430e82c
It doesn't happen all the time, but a good 90% on my machine, so it's fairly reproducible. @ankur22 was also able to reproduce it on macOS. Note that it doesn't happen in CI, since failed checks still exit the process with code 0, but I actually haven't seen it fail the check either.
We thought we addressed all navigation race conditions in #480, but apparently not, or this is a recent regression. 😞
The text was updated successfully, but these errors were encountered: