Replace PhantomJS with Chrome in Karma test runner (2nd attempt)
This is a continuation of !12036 (merged) which was reverted in !12137 (merged) due to some transient CI failures.
Closes #33633 (closed)
Related to: #30876 (moved)
Changes from !12036 (merged):
- added the
--no-sandboxflag to Chrome when it launches (this has documented compatibility issues when running in Docker) - added and enabled chrome verbose output logging to a file named
chrome_debug.logwhich will be saved in the CI job's artifacts. if we start to get any transient errors in the future, this log should be useful - upgraded
karmato a newer version which properly displays stderr output when a browser fails to launch - upgraded
jasmine-coreto a newer version which should be less susceptible to theDisconnected, because no message in 10000 ms.errors as seen here.
Edited by username-removed-636429
Merge request reports
Activity
mentioned in issue #30876 (moved)
added 12 commits
- 828f3fd1...a1695253 - 2 commits from branch
master - e9bd861f - replace PhantomJS with headless Chrome as karma test runner
- 60f7a43f - fix incorrect equals assertion
- d44149e6 - remove phantomjs from our frontend dev dependencies
- e45989b0 - test new docker image with headless chrome
- 2111712c - update karma job to use chrome build image created by gitlab-build-images!41 (merged)
- 8b069dbb - remove phantomjs-specific test hacks
- 86a2d9bf - add CHANGELOG.md entry for !12036 (merged)
- 413f7d31 - force chrome to produce debug output as it runs in CI
- 37577031 - upgrade karma to v1.7.0
- d70be8f8 - run chrome with --no-sandbox flag to get around docker privilege limitations
Toggle commit list- 828f3fd1...a1695253 - 2 commits from branch
added 1 commit
- 7b4f8aa4 - upgrade jasmine to attempt to resolve browser timeout issues
added 1 commit
- 7b4f8aa4 - upgrade jasmine to attempt to resolve browser timeout issues
added 1 commit
- 7b4f8aa4 - upgrade jasmine to attempt to resolve browser timeout issues
added 1 commit
- 7b4f8aa4 - upgrade jasmine to attempt to resolve browser timeout issues
added 1 commit
- d5ab729d - remove debug flag, but continue to log chrome output
added 1 commit
- 132be812 - fix frontend test failures after jasmine upgrade
added 1 commit
- 132be812 - fix frontend test failures after jasmine upgrade
@timzallmann can you review/merge this for me?
Here's a quick summary of the changes since the last MR (!12036 (merged)) which needed to be reverted:
- added the
--no-sandboxflag to Chrome when it launches (this has documented compatibility issues when running in Docker) - added and enabled chrome verbose output logging to a file named
chrome_debug.logwhich will be saved in the CI job's artifacts. if we start to get any transient errors in the future, this log should be useful - upgraded
karmato a newer version which properly displays stderr output when a browser fails to launch - upgraded
jasmine-coreto a newer version which should be less susceptible to theDisconnected, because no message in 10000 ms.errors as seen here.
- added the
@mikegreiling Thank you for digging into it. Lets try it out.
mentioned in commit 446f3787
Please register or sign in to reply