-
Type: Task
-
Status: Resolved
-
Priority: Major
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: CI/CD
-
Tags:
-
Team:UI
SauceLabs tests fail often with:
17:00:54 > karma start --package core --coverage
17:00:54
17:01:21
17:01:21 START:
17:01:43 [91m15 12 2020 17:01:41.550:ERROR [SaucelabsLauncher]: [39mError: 15 Dec 17:01:41 - Sauce Connect could not establish a connection.
17:01:43 15 Dec 17:01:41 - Please check your firewall and proxy settings.
17:01:43 15 Dec 17:01:41 - Goodbye.
17:01:43
17:01:43 at Socket.cp.stdout.on.data (/home/jenkins/agent/workspace/nuxeo_nuxeo-elements_PR-339/node_modules/saucelabs/build/index.js:320:25)
17:01:43 at Socket.emit (events.js:193:13)
17:01:43 at Socket.EventEmitter.emit (domain.js:481:20)
17:01:43 at addChunk (_stream_readable.js:295:12)
17:01:43 at readableAddChunk (_stream_readable.js:276:11)
17:01:43 at Socket.Readable.push (_stream_readable.js:231:10)
17:01:43 at Pipe.onStreamRead (internal/stream_base_commons.js:154:17)
Under ELEMENTS-1294, we made a workaround for this where we put some sleep time between test suites. This is not a clean solution and we still have failures.
- is related to
-
ELEMENTS-1294 Fix saucelabs test run
- Resolved