New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 762883 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

veyron_mickey-release:1470 failed

Project Member Reported by yamaguchi@chromium.org, Sep 7 2017

Issue description

veyron_mickey-release:1470 failed

Builders failed on: 
- veyron_mickey-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/veyron_mickey-release/1470


Autotest instance created: cautotest
09-06-2017 [20:59:49] Created suite job: http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=140294179
09-06-2017 [21:06:00] Suite job is finished.
09-06-2017 [21:06:00] Start collecting test results and dump them to json.
Suite job   [ FAILED ]
Suite job     FAIL:             500 Internal Server Error          #powered_by {         margin-top: 20px;         border-top: 2px solid black;         font-style: italic;     }      #traceback {         color: red;     }                    500 Internal Server Error         The server encountered an unexpected condition which prevented it from fulfilling the request.         Traceback (most recent call last):   File "/usr/lib/python2.7/dist-packages/cherrypy/_cprequest.py", line 656, in respond     response.body = self.handler()   File "/usr/lib/python2.7/dist-packages/cherrypy/lib/encoding.py", line 188, in __call__     self.body = self.oldhandler(*args, **kwargs)   File "/usr/lib/python2.7/dist-packages/cherrypy/_cpdispatch.py", line 34, in __call__     return self.callable(*self.args, **self.kwargs)   File "/home/chromeos-test/chromiumos/src/platform/dev/devserver.py", line 1315, in list_suite_controls     kwargs['suite_name']).splitlines()]   File "/home/chromeos-test/chromiumos/src/platform/dev/common_util.py", line 189, in GetControlFileListForSuite     return '\n'.join(ast.literal_eval(fd.read())[suite_name])   File "/usr/lib/python2.7/ast.py", line 49, in literal_eval     node_or_string = parse(node_or_string, mode='eval')   File "/usr/lib/python2.7/ast.py", line 37, in parse     return compile(source, filename, mode, PyCF_ONLY_AST)   File "unknown", line 0          ^ SyntaxError: unexpected EOF while parsing           Powered by CherryPy 3.2.2            

 
Cc: jintao@chromium.org tbroch@chromium.org
Owner: jrbarnette@chromium.org
I don't know much about this, but I guessed this is error when rebooting DUT in the auto update test.
Will you verify it?

host: chromeos4-row3-rack10-host6, status: Running, locked: False diagnosis: Working
Last 10 jobs within 3:18:00:
1250512 Reset started on: 2017-09-06 20:54:57 status PASS
1250442 Repair started on: 2017-09-06 20:41:54 status PASS
1250438 Reset started on: 2017-09-06 20:41:23 status FAIL
140636139 veyron_mickey-release/R60-9592.92.0/paygen_au_stable/autoupdate_EndToEndTest_paygen_au_stable_full_9592.92.0 started on: 2017-09-06 20:19:05 status Completed
1250177 Reset started on: 2017-09-06 20:18:42 status PASS
140631343 veyron_mickey-release/R60-9592.92.0/au/autoupdate_Rollback started on: 2017-09-06 20:09:34 status Completed
1250093 Reset started on: 2017-09-06 20:09:15 status PASS
140630793 veyron_mickey-release/R60-9592.92.0/bvt-inline/login_SameSessionTwice started on: 2017-09-06 20:08:23 status Completed
1250081 Reset started on: 2017-09-06 20:08:01 status PASS
140630787 veyron_mickey-release/R60-9592.92.0/bvt-inline/security_StatefulPermissions started on: 2017-09-06 20:07:21 status Completed

The Suite job failed because of an error from some devserver.
I'm not sure what happened, but the failure happened before any
DUT could be assigned work (in fact, it's likely that the failure
prevented any DUT from being assigned work).

Labels: Hotlist-Fixit Pri-3 Type-Bug
Owner: ----
Build artifacts are here:
    https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/veyron_mickey-release/R63-9918.0.0

If you download the file test_suites.tar.bz2, and extract from it
"autotest/test_suites/suite_to_control_file_map", you'll find that the
extracted file is empty.  The file is supposed to contain a quarter
MByte JSON blob.

AFAICT, that file is supposed to be created during build_packages by
the "autotest-all" ebuild.  So, something presumably went wrong there.
However, looking in the build's "BuildPackages" stage, nothing is
reported.

As best I can tell, it means these lines in pkg_postinst in the ebuild
failed silently:
    python -B "${root_autotest_dir}/site_utils/control_file_preprocessor.py" \
        -a "${root_autotest_dir}" \
        -o "${root_autotest_dir}/test_suites/${SUITE_TO_CONTROL_MAP}"

To make progress, someone would have to go instrument the code so that
it won't fail silently.  That's likely to be easier said than done,
since the source of the failure isn't known.

However, none of this is likely worth doing unless there's some prospect
for a recurrence.  So, unless this problem becomes frequent enough to
warrant debug: P3 and no owner.

Comment 4 by tbroch@chromium.org, Sep 14 2017

Cc: -tbroch@chromium.org
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be archived. Thank you.

Sign in to add a comment