This machine is sending different environment parameters than the first machine that started this parallel run.
See original GitHub issueHey there! Iβm receiving this error just recently in my Github Actions that run multiple tests in parallel:
/opt/hostedtoolcache/node/14.20.1/x64/bin/npx cypress cache list
βββββββββββ¬ββββββββββββββββββββ
β version β last used β
βββββββββββΌββββββββββββββββββββ€
β 10.3.0 β a few seconds ago β
βββββββββββ΄ββββββββββββββββββββ
[2200:1004/193837.782206:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[2200:1004/193837.793000:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
Missing baseUrl in compilerOptions. tsconfig-paths will be skipped
You passed the --parallel flag, but we do not parallelize tests across different environments.
This machine is sending different environment parameters than the first machine that started this parallel run.
The existing run is: https://dashboard.cypress.io/projects/<:)>/runs
In order to run in parallel mode each machine must send identical environment parameters such as:
- specs
- osName
- osVersion
- browserName
- browserVersion (major)
This machine sent the following parameters:
{
"osName": "linux",
"osVersion": "Ubuntu - 20.04",
"browserName": "Chrome",
"browserVersion": "106.0.5249.91",
"specs": [
...
]
}
https://on.cypress.io/parallel-group-params-mismatch
Test run failed, code 1
More information might be available above
Cypress module has returned the following error message:
Could not find Cypress test run results
Error: Could not find Cypress test run results
I can confirm that a view of the jobs are running Chrome 105 and other Chrome 106. Here is my workflow configuration:
jobs:
transact:
name: Transact
runs-on: ubuntu-latest
strategy:
# when one test fails, DO NOT cancel the other
# containers, because this will kill Cypress processes
# leaving the Dashboard hanging ...
# https://github.com/cypress-io/github-action/issues/48
fail-fast: false
matrix:
# Specifies the concurrency of tests to run
container: [1, 2, 3, 4, 5]
steps:
- name: Run Cypress tests
id: e2e-tests
uses: cypress-io/github-action@v4
with:
browser: chrome
record: true
parallel: true
group: 'Transact'
config: baseUrl=${{ github.event.inputs.baseUrl }}
env: apiHost=${{ github.event.inputs.apiHost }}
env:
CYPRESS_RECORD_KEY: ${{ secrets.TRANSACT_CYPRESS_RECORD_KEY }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Is Github using different versions of chrome on their ubuntu-latest
image? π€
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:15 (1 by maintainers)
Top Results From Across the Web
parallel-group-params-mismatch caused by browser #121
This machine is sending different environment parameters than the first machine that started this parallel run. In order to run in parallel modeΒ ......
Read more >Grouping parallel runs in one entry on Cypress.io using Gitlab CI
This machine is sending different environment parameters than the first machine that started this parallel run. The existing run is:Β ...
Read more >Error Messages | Cypress Documentation
This machine is sending different environment parameters than the first machine that started this parallel run. In order to run in parallel mode...
Read more >Cypress testing: Running tests in parallel - Valor Software
This provides the possibility to run tests on different machines inside the first stage. You can add as many scripts as you need,...
Read more >Running Programs With the mpirun Command
This manuals also describes how to execute parallel programs, a. ... The mpirun command uses MCA (Multiple Component Architecture) parameters to passΒ ...
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 FreeTop 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
Top GitHub Comments
Have got this working with setup-chrome after finding this comment https://github.com/cypress-io/github-action/issues/518#issuecomment-1210979047
As we use a custom command, had to specify
--browser ${{ env. BROWSER_PATH }}
in that commandAny updates on this? It happens for us almost monthly and seems to be whenever chrome updates! I agree that the check against browser matching for environments could be configured to solve for this issue and be less strict