iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

ci: ensure saucelabs test output is human readable (#34277)

Browse Source 
Currently the Saucelabs test output (also an issue in the POC bazel
saucelabs master-only cronjob), is very verbose because two Karma
reporters conflict. Basically resulting in the progress messages
being printed in new lines (while they usually are just updated
using a tty cursor reset).

PR Close #34277
This commit is contained in:
Paul Gschwendtner 2019-12-12 10:39:10 +01:00 committed by Kara Erickson
parent 6d3a25d897
commit 04ab03664d
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
karma-js.conf.js
View File

@ -116,8 +116,6 @@ module.exports = function(config) {
'/base/npm/': '/base/', '/base/npm/': '/base/',
}, },
reporters: ['dots'],
sauceLabs: { sauceLabs: {
testName: 'Angular2', testName: 'Angular2',
retryLimit: 3, retryLimit: 3,
@ -145,11 +143,19 @@ module.exports = function(config) {
browserDisconnectTimeout: 180000, browserDisconnectTimeout: 180000,
browserDisconnectTolerance: 3, browserDisconnectTolerance: 3,
browserNoActivityTimeout: 300000, browserNoActivityTimeout: 300000,
} };
// Workaround for: https://github.com/bazelbuild/rules_nodejs/issues/1431. The idea is
// that we do no not allow `@bazel/karma` to add the `progress` reporter.
Object.defineProperty(conf, 'reporters', {
enumerable: true,
get: () => ['dots'],
set: () => {},
});
// When running under Bazel with karma_web_test, SAUCE_TUNNEL_IDENTIFIER and KARMA_WEB_TEST_MODE // When running under Bazel with karma_web_test, SAUCE_TUNNEL_IDENTIFIER and KARMA_WEB_TEST_MODE
// will only be available when `--config=saucelabs` is set. See //:test_web_all target // will only be available if they are part of the Bazel action environment. More details in the
// and /.bazelrc. // "scripts/saucelabs/run-bazel-via-tunnel.sh" script.
if (process.env['SAUCE_TUNNEL_IDENTIFIER']) { if (process.env['SAUCE_TUNNEL_IDENTIFIER']) {
console.log(`SAUCE_TUNNEL_IDENTIFIER: ${process.env.SAUCE_TUNNEL_IDENTIFIER}`); console.log(`SAUCE_TUNNEL_IDENTIFIER: ${process.env.SAUCE_TUNNEL_IDENTIFIER}`);