Bug #45148
Updated by Tatjana Dehler about 4 years ago
The 'jenkins test dashboard' command is failing on master:
<pre>
[11:03:56] E/launcher - ENOENT: no such file or directory, open 'fs.js'
[11:03:56] E/launcher - Error: ENOENT: no such file or directory, open 'fs.js'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at PrettyStacktraceProcessor.retrieveErrorContext (/home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/processors/pretty-stacktrace-processor.js:60:28)
at /home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/processors/pretty-stacktrace-processor.js:51:42
at Array.forEach (<anonymous>)
at PrettyStacktraceProcessor.prettifyStack (/home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/processors/pretty-stacktrace-processor.js:48:35)
at PrettyStacktraceProcessor.displayErrorMessages (/home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/processors/pretty-stacktrace-processor.js:38:32)
at PrettyStacktraceProcessor.displaySpecErrorMessages (/home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/processors/pretty-stacktrace-processor.js:27:109)
at /home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/display/execution-display.js:55:45
at /home/jenkins-build/build/workspace/ceph-dashboard-pull-requests/src/pybind/mgr/dashboard/frontend/node_modules/jasmine-spec-reporter/built/display/logger.js:21:19
[11:03:56] E/launcher - Process exited with error code 199
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ceph-dashboard@0.0.0 e2e:ci: `npm run env_build && npm run e2e:update && ng e2e --dev-server-target --webdriverUpdate=false`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ceph-dashboard@0.0.0 e2e:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/jenkins-build/.npm/_logs/2020-04-16T11_03_56_897Z-debug.log
2020-04-16T11:03:58.821+0000 7f350b8713c0 -1 WARNING: all dangerous and experimental features are enabled.
2020-04-16T11:03:58.821+0000 7f350b8713c0 -1 WARNING: all dangerous and experimental features are enabled.
2020-04-16T11:03:58.821+0000 7f350b8713c0 -1 WARNING: all dangerous and experimental features are enabled.
2020-04-16T11:03:58.909+0000 7f51b61f23c0 -1 WARNING: all dangerous and experimental features are enabled.
2020-04-16T11:03:58.909+0000 7f51b61f23c0 -1 WARNING: all dangerous and experimental features are enabled.
2020-04-16T11:03:58.913+0000 7f51b61f23c0 -1 WARNING: all dangerous and experimental features are enabled.
Build step 'Execute shell' marked build as failure
Setting status of d7f7f351e6169de886afc11fd69650f8d933ad25 to FAILURE with url https://jenkins.ceph.com/job/ceph-dashboard-pull-requests/3856/ and message: 'ceph dashboard tests failed
'
Using context: ceph dashboard tests
Finished: FAILURE
</pre>
https://jenkins.ceph.com/job/ceph-dashboard-pull-requests/3856/consoleFull#-85362248744e9240e-b50a-4693-bac0-8a991bac86ac
https://jenkins.ceph.com/job/ceph-dashboard-pull-requests/3877/consoleFull#-85362248744e9240e-b50a-4693-bac0-8a991bac86ac
I do also see the error when running the run-frontend-e2e-tests.sh script on my local docker environment.