gauge: Unable to run in parallel with more than 14 nodes
Expected behavior
Previous Gauge versions used to run fine with up to 30 in parallel
Actual behavior
We run our tests using Saucelabs headless feature. Previous versions had no problems running in parallel with up to 30-35 in parallel
Currently, If select to run with more than 10 in parallel I get this following error bellow. Running with 10. works fine.
SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [Flash] Starting progress reporting at http://127.0.0.1:39277 Executing in 30 parallel streams. Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Failed to start runner. Timed out connecting to java Successfully generated html-report to => …/reports/staging/html-report/index.html
Successfully generated json-report to => …t/reports/staging/json-report
Specifications: 0 executed 0 passed 0 failed 0 skipped Scenarios: 0 executed 0 passed 0 failed 0 skipped
Total time taken: 30.353s 34mINFO[m] [1m----------------------------------------------------------------------- 34mINFO[m] [1;32mBUILD SUCCESS[m 34mINFO[m] [1m----------------------------------------------------------------------- 34mINFO[m] Total time: 40.399 s 34mINFO[m] Finished at: 2020-02-21T12:48:33-05:00 34mINFO[m] Final Memory: 28M/393M 34mINFO[m] [1m------------------------------------------------------------------------
Gauge version
Gauge version: 1.0.7
Commit Hash: ed7b4fd6
Plugins
-------
flash (0.0.2)
html-report (4.0.9)
java (0.7.4)
json-report (0.3.3)
screenshot (0.0.1)
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (10 by maintainers)
Commits related to this issue
- use singleThreadExecutor instead of custom executor, fizes getgauge/gauge#1588 — committed to getgauge/gauge-java by sriv 4 years ago
- use singleThreadExecutor instead of custom executor, fixes getgauge/gauge#1588 Signed-off-by: sriv <srikanth.ddit@gmail.com> — committed to getgauge/gauge-java by sriv 4 years ago
- use singleThreadExecutor instead of custom executor, fixes getgauge/gauge#1588 (#433) Signed-off-by: sriv <srikanth.ddit@gmail.com> — committed to getgauge/gauge-java by sriv 4 years ago
@sriv Bingo!!!
That was it!!! I had enable_multithreading set to false. (I missed this one, my bad)
Now works fine. The below is running 25 in parallel with enable_multithreading set to true.
We can put this issue to rest once and for all
Thanks. I’ll have to ask Devops to increase memory. I’ll get back to you with some results very soon.
I’m going to create a sample project that points to our Saucelabs account with 30 nodes. In this way you can run it from your side and debug it.
It’ll take few days to set up.