Exit code 137 means the process was killed with SIGKILL (128 + 9). In CI that's nearly always the kernel's OOM killer stepping in because the job ran out of memory.
Published
Why this happens
Browsers, the app under test, and the test runner together use more memory than the runner has
A Docker container has a memory limit lower than what the job needs
Too many parallel test workers or browser instances are running at once
The job hit its timeout and the platform force-killed it
How to fix it
Cut parallelism first (fewer workers, one browser project per job) and see whether the kill goes away
Move to a larger runner, or raise the container's memory limit
Shard the suite across several jobs instead of running everything on one machine
Check the step's duration too. If it stopped right at the timeout, this is a hang, not a memory problem