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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1834052

Title:
  autopkgtest failures: Chromium-Related in Tests

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in kopano-webapp package in Ubuntu:
  New

Bug description:
  Hello.

  Currently, the kopano-webapp autopkgtests are failing.  Three of these
  are related to Chromium crashes/failures (possibly because they're
  snapped) within the Selenium calls.

  The fourth is a snap related issue in general.

  These autopkgtest failures are blocking HTTPD packages in Proposed
  (nginx, apache, etc.)

  
  ------
  Relevant Links:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/k/kopano-webapp/20190624_082152_0ef6d@/log.gz

  arm64:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/arm64/k/kopano-
  webapp/20190624_084645_0ef6d@/log.gz

  armhf:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/k/kopano-
  webapp/20190624_082623_0ef6d@/log.gz

  i386:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/i386/k/kopano-
  webapp/20190624_082523_0ef6d@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1834052/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to