Re: Issue 574870 in chromium: [sanity] dummy_PassServer.sanity_SERVER_JOB Failure on veyron-b-group canary

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: d...@chromium.org
Labels: -Infra -Restrict-View-Google Type-Bug Pri-2 OS-Chrome
Build-HardwareLab

Comment #1 on issue 574870 by jrbarne...@chromium.org: [sanity]
dummy_PassServer.sanity_SERVER_JOB Failure on veyron-b-group canary
https://code.google.com/p/chromium/issues/detail?id=574870

Here's the suite job:

http://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=50732932

The suite created this server-side job:

http://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=50732959

Here's the full text of status.log from the job:
FAIL ---- ---- timestamp=1452089968 localtime=Jan 06 06:19:28 Failed to
setup container for test: Command <sudo lxc-ls -P
/usr/local/autotest/containers -f -F name,state> failed, rc=139, Command
returned non-zero exit status
* Command:
sudo lxc-ls -P /usr/local/autotest/containers -f -F name,state
Exit status: 139
Duration: 0.918902158737
. Check logs in ssp_logs folder for more details.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #2 on issue 574870 by d...@chromium.org: [sanity]

dummy_PassServer.sanity_SERVER_JOB Failure on veyron-b-group canary
https://code.google.com/p/chromium/issues/detail?id=574870

Only message about lxc I can found around that time is this one:
Jan 6 06:19:25 cros-autotest-shard5.hot.corp.google.com kernel:
[1519694.350964] lxcbr0: port 5(veth1EOKRV) entered disabled state

That seems to be related to the container being destroyed during cleanup.

The lxc-ls command failed with 139 (Segmentation fault), it could be some
flake.