github-action: parallel-group-params-mismatch caused by browser

We use parallelized actions with browser: chrome, it already happened twice (in ~40 runs) that Chrome version caused fail on “parallel-group-params-mismatch”. First job used the older version (e.g. “80.0.3987.132”) and others newer (e.g. “80.0.3987.149”).

Restarting the job of course does not solve anything as the ID of the action is still the same and with the older version of Chrome. Only solution is to trigger a new run.

Is there please any suggestion on how to solve this? (We wouldn’t mind if matching would be just on major version of Chrome, but sadly I did not figure how to do that.)

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 18 (7 by maintainers)

Most upvoted comments

@CharlesStover I am having the same issue with with Chrome

gavinhenderson on Nov 2, 2022

FWIW my workaround https://github.com/cypress-io/cypress/issues/7199#issuecomment-1143628102

choonkeat on Jun 1, 2022

I’m getting a similar issue, in both cypress-io/github-action@v2 and cypress-io/github-action@v4.

The first 2 runs use Edge 106, but the third run uses Edge 107, which throws the parallel-group-params-mismatch error. I changed it from 3 to only 2 groups, and the error persists: the first uses 106, but the second uses 107.

This is only happening for Edge. Chrome passes successfully.

This is definitely unintuitive, because the configuration is only set to browser: edge, and there’s no way to specify a version. It’s weird to see them automatically choose the wrong version then fail for doing so.

quisido on Oct 29, 2022

Happening to me as well right now. Bouncing between Chrome 106 and 107.

chinanderm on Nov 2, 2022