I can now reproduce the failure by running the test with nosetests3
manually.
Removing the "--log-path=/tmp/chromedriver.log" service arg fixes the
issue. The confined chromedriver bails out when it fails to write there:
$ /snap/bin/chromium.chromedriver --log-path=/tmp/chromedriver.log
Starting ChromeDriver 75.0.3770.90
(a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}) on
port 9515
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to
prevent access by malicious code.
Failed to redirect stderr to log file.
Unable to initialize logging. Exiting...
Given that the log file isn't exposed as a retrievable artefact when
autopkgtests are run, I suggest we just remove it.
If it turns out that a significant number of existing selenium tests do the
same, we could consider patching chromedriver in the snap to ignore that
argument, instead of bailing out.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834052
Title:
autopkgtest failures: Chromium-Related in Tests
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
