Chrome parallel-group-params-mismatch error
See original GitHub issueWe 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](https://user-images.githubusercontent.com/4401230/157884477-7284d25f-f033-4dcf-a269-0bb80dc4d4bd.png)
The other containers start a minute later and show us this error :
![Capture d’écran 2022-03-11 à 15 12 46](https://user-images.githubusercontent.com/4401230/157884483-7109923b-13b6-4a9c-88d7-dc160dc8fc93.png)
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:
- Created 2 years ago
- Reactions:20
- Comments:9
Top 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 >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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!
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