Open ankur22 opened 1 year ago
I had a quick look. Unfortunately there's two issues:
browser
instance, there's a chance that either the iterEnd
or exit
events would have fired which will clear the browser
before the system can check the state of chrome.I believe the browser
is being set just before or as Chrome is ending. The process of chrome ending starts the termination of the whole test run, which in turn clears the browser
away. When the test comes to retrieve the browser
it's no longer there, and that is why we print the incorrect reason for the test terminating.
Brief summary
When a test script is ran against a containerised version of k6 and chrome on a ARM machine, it will result in the following error:
When the same script is ran on a machine running on a AMD64 processor the test passes without an issue.
I believe the issue is that Chrome is crashing in the running container but we're masking the original issue with the wrong error message.
xk6-browser version
v0.46.0
OS
Mac on ARM
Chrome version
NA
Docker version and image (if applicable)
Latest
Steps to reproduce the problem
docker run --rm --cap-add=SYS_ADMIN -i grafana/k6:0.46.0-with-browser run - <test.js
Expected behaviour
The test passes as expected.
Actual behaviour
The test fails with: