Issue 643767 link

Starred by 2 users

Issue metadata

Status:	Archived
Owner:	█ dshi@chromium.org Last visit > 30 days ago
Closed:	Sep 2016
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
Proj-Moblab VerifyIn-55 VerifyIn-56 VerifyIn-57 VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Blocking:
issue chrome-os-partner:54747

moblab: Failed to setup container for test while doing mobalb

Project Member Reported by gwendal@chromium.org, Sep 2 2016

Issue description

The status log indicates:
Failed to setup container for test: not all arguments converted during string formatting. Check logs in ssp_logs folder for more details.

ssp_logs/debug enclosed.

There are errors around creating the container:
08/24 11:27:23.529 DEBUG|        base_utils:0177| Running 'sudo lxc-clone -p /mnt/moblab/containers -P /mnt/moblab/containers base test_3168_1472009243_15208  '
08/24 11:29:03.897 DEBUG|          autoserv:0350| Received SIGTERM

And destroying it:
08/24 11:30:07.781 DEBUG|        base_utils:0177| Running 'sudo lxc-destroy -P /mnt/moblab/containers -n test_3168_1472009243_15208 -f'
08/24 11:30:07.793 ERROR|               lxc:0232| Command <sudo lxc-destroy -P /mnt/moblab/containers -n test_3168_1472009243_15208 -f> failed, rc=1, Command returned non-zero exit status
* Command:.
    sudo lxc-destroy -P /mnt/moblab/containers -n test_3168_1472009243_15208
    -f
Exit status: 1
Duration: 0.00593495368958

stderr:
Container is not defined
08/24 11:30:07.817 INFO |        server_job:0128| FAIL  ----  ----  timestamp=1472009407  localtime=Aug 24 11:30:07 Failed to setup container for test: not all arguments converted during string formatting. Check logs in ssp_logs folder for more det>

Comment 1 by dshi@chromium.org, Sep 2 2016

What's the IP of your moblab? Can I ssh in and do some test?

Comment 2 by gwendal@chromium.org, Sep 2 2016

Blocking: chrome-os-partner:54747

Sorry, it is a vendor moblab.

gs://chromeos-moblab-asus/results/2c:60:0c:7c:60:ff/6d85f0a8-8d09-11e5-a441-d8fc93c5ef54/

Comment 3 by dshi@chromium.org, Sep 2 2016

I need the full log of that failed test.

There are some test using server-side packaging passed just fine:
gs://chromeos-moblab-asus/results/2c:60:0c:7c:60:ff/6d85f0a8-8d09-11e5-a441-d8fc93c5ef54/2812-moblab/192.168.231.102

So that failure could be test specific.

Comment 4 by gwendal@google.com, Sep 2 2016

The test that fail is 3168-moblab.

Comment 5 by dshi@chromium.org, Sep 2 2016

Cc: -dshi@chromium.org
Owner: dshi@chromium.org

08/24 11:27:23.529 DEBUG|        base_utils:0177| Running 'sudo lxc-clone -p /mnt/moblab/containers -P /mnt/moblab/containers base test_3168_1472009243_15208  '
08/24 11:29:03.897 DEBUG|          autoserv:0350| Received SIGTERM
08/24 11:29:03.897 DEBUG|          autoserv:0353| Finished writing to pid_file. Killing process.

So it seems that the test was aborted during lxc-clone is running. So the failure is not really an infra issue, but the error makes it looks like the test failed because of infra. I will add some error handling to make the failure not misleading.

Comment 6 by krk@chromium.org, Sep 15 2016

Status: Assigned (was: Untriaged)

Project Member

Comment 7 by bugdroid1@chromium.org, Sep 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/65374e29419788071879c6083a6aeb8a267526fe

commit 65374e29419788071879c6083a6aeb8a267526fe
Author: Dan Shi <dshi@google.com>
Date: Thu Sep 15 23:14:05 2016

[autotest] Fix a bug in ssp exception handling

sys.exc_info() returns a tuple, thus following code will fail:
'Exception: %s' % sys.exc_info()

Also cleaned up an issue with local variable.

BUG= chromium:643767 
TEST=None

Change-Id: I272a361db11d772860c088c533af3dc6b734d58b
Reviewed-on: https://chromium-review.googlesource.com/386085
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Simran Basi <sbasi@chromium.org>

[modify] https://crrev.com/65374e29419788071879c6083a6aeb8a267526fe/server/autoserv