New issue
Advanced search Search tips

Issue 631932 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 630698
Owner: ----
Closed: Jul 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"ui_arc_unittests (with patch)" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 27 2016

Issue description

"ui_arc_unittests (with patch)" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 4 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKAsSBUZsYWtlIh11aV9hcmNfdW5pdHRlc3RzICh3aXRoIHBhdGNoKQw.


 

Comment 1 by vabr@chromium.org, Jul 27 2016

Mergedinto: 630698
Status: Duplicate (was: Untriaged)
This is very similar to  bug 630698 . The essential part of error output:

Traceback (most recent call last):
  File "/b/c/b/linux_chromeos/src/infra/scripts/legacy/scripts/slave/runtest.py", line 560, in <module>
    sys.exit(main())
  File "/b/c/b/linux_chromeos/src/infra/scripts/legacy/scripts/slave/runtest.py", line 550, in main
    return _Main(options, args, extra_env)
  File "/b/c/b/linux_chromeos/src/infra/scripts/legacy/scripts/slave/runtest.py", line 231, in _Main
    'True'))
  File "/b/c/b/linux_chromeos/src/infra/scripts/legacy/scripts/slave/xvfb.py", line 106, in StartVirtualX
[Running on builder: "linux_chromium_chromeos_rel_ng"]
DBUS_SESSION_BUS_ADDRESS env var not found, starting dbus-launch
 setting DBUS_SESSION_BUS_ADDRESS to unix:abstract=/tmp/dbus-fS4FERRRCQ,guid=97d7ed1076553d703ed8fe8700000620
 setting DBUS_SESSION_BUS_PID to 8088
Verifying Xvfb is not running ...
Verifying Xvfb has started...
xdisplaycheck failed after 30 seconds.
xdisplaycheck output:
> Failed to connect to :9
Xvfb exited, code 1
Xvfb output:
> 
> Fatal server error:
> Server is already active for display 9
> 	If this server is no longer running, remove /tmp/.X9-lock
> 	and start again.
> 
Stopping Xvfb with pid 8092 ...
... killing failed, presuming unnecessary.
Xvfb pid file removed
 killed dbus-daemon with PID 8088
 cleared DBUS_SESSION_BUS_ADDRESS environment variable
    raise Exception(logs)
Exception: Failed to connect to :9

Sign in to add a comment