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

Issue 655680 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

autotest: status file only contains the last test status.

Project Member Reported by gwendal@chromium.org, Oct 13 2016

Issue description

This is not a new bug, but it has bothered me for a while, and I don't find any explanation:


Running StorageQualBase.test, a sequence running a list of test, 'status' in '/tmp/test_that_latest/results-1-StorageQualBase.test/hardware_StorageQualBase/' file would only contains the last test result, while status.log would contain all the tests statuses. Same thing for /tmp/test_that_latest/results-1-StorageQualBase.test/, where only the last sysinfo call would be logged.

Why is status truncated? status_logger.record_logger is appending to all status files.

The problem is create_report in html_report.py is using 'status' for building its HTML result page, showing only the last test.




 
status.log
1.2 KB View Download
status
204 bytes View Download
status
543 bytes View Download
status.log
7.6 KB View Download
It looks like 'status.log' comes from the server side, 'status' from the client side.
Given each job use the same base result_dir, each client job overwrite the 'status' file written by the previous client job.
Doesn't it make the status file useless given a server job always runs several client job (sysinfo.before, job, sysinfo.after)?

Comment 2 by dshi@chromium.org, Oct 13 2016

Components: -Tests Infra>Client>ChromeOS
Labels: current-issue Hotlist-Fixit
Seems to be some issue with the infra. This can also apply to a server side test runs multiple client side tests.

Comment 3 by sbasi@chromium.org, Oct 13 2016

Cc: akes...@chromium.org
Labels: -current-issue
Aviv,

Could you find an owner?
Status: Archived (was: Untriaged)
This bug has not been touched in over a year.  It is probably no longer relevant.

Sign in to add a comment