question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Chrome parallel-group-params-mismatch error

See original GitHub issue

We use parallelized actions with browser: chrome, it worked well until yesterday. Now sometimes (not always) we have this behavior :

A first container starts with apparently Chrome 98 :

Capture d’écran 2022-03-11 à 15 12 17

The other containers start a minute later and show us this error :

Capture d’écran 2022-03-11 à 15 12 46

It says the specs mismatch, I guess it is because of the Chrome version here being Chrome 99 ?

So only 1 container (the first starting) goes ✅ and the others fail like above ❌

The configuration of our Github Action is like this :

- name: Cypress run
              uses: cypress-io/github-action@v2
              with:
                  browser: chrome
                  build: npm run build
                  config-file: cypress/cypress-ci.json
                  group: "Chrome"
                  parallel: true
                  record: true
                  start: [our starting script]
                  wait-on: [our local url]

I don’t see a way of specifying a particular browser version with this action, am I missing something ?

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:20
  • Comments:9

github_iconTop GitHub Comments

7reactions
paulzakincommented, Aug 10, 2022

I solved this problem by avoiding the browser bundled with GitHub Actions.

Basically, I install the latest version of chromium and just use that.

Here’s what that code looks like in our GitHub action.

If the Cypress team doesn’t want to update the action itself to handle this mismatch, it might make sense to provide some examples in the documentation for how to avoid this problem!

- uses: browser-actions/setup-chrome@latest
- run: |
    echo "BROWSER_PATH=$(which chrome)" >> $GITHUB_ENV

- name: Run Cypress tests 🚀
  uses: cypress-io/github-action@v4
  with:
    install: false
    record: true
    parallel: true
    browser: "${{ env.BROWSER_PATH }}"
    start: "your start command"
  env:
    CYPRESS_RECORD_KEY: ${{ secrets.recordKey }}
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }
7reactions
jebarjonetcommented, Jun 1, 2022

For information the situation solved itself after a day or two but it is still happening sometimes, like today for a mismatch between Chrome 101 and Chrome 102

Read more comments on GitHub >

github_iconTop Results From Across the Web

Grouping parallel runs in one entry on Cypress.io using Gitlab CI
You are triggering two parallel runs, with each parallel run setting up two browsers. As the error says, this is not expected -...
Read more >
Test your landing page - Google Ads Help
The landing page has more parameters than the final URL. Landing page has URL mismatch, All, The landing page domain doesn't match the...
Read more >
Parallel Tracking FAQ | AdWords API (Deprecated)
If you currently append static parameters while redirecting to the landing page you should enter those in Google Ads in the finalUrl or ......
Read more >
Destination Mismatch Google Ads: Why Your Ads Get ...
For web-based campaigns, it is recommended to use the Branch link instead of the tracking template URL. This is because parallel tracking is...
Read more >
Workflow errors - Google Cloud
Errors for Workflows might be raised, for example, by failed HTTP requests, ... The associated value is a string giving details about the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found