Moblab StorageQualTrim.quick keeps aborting two tests. |
|||||||||||||
Issue descriptionVersion: Moblab M53-STABLE-9 8530.95.0 OS: ChromeOS What steps will reproduce the problem? (1) Run the StorageQualTrim.quick suite What is the expected output? All jobs should pass. What do you see instead? http://100.96.48.80/afe/#tab_id=view_job&object_id=680 http://100.96.48.80/afe/#tab_id=view_job&object_id=679 These tests seem to have been having issues for a while as I checked some older test runs and they were aborted as well. The specific tests are: hardware_StorageQualTrimStress_suspend_0 hardware_StorageQualTrimStress_suspend_1 The suite test run is here: http://100.96.48.80/afe/#tab_id=view_job&object_id=669
,
Dec 7 2016
Hi Tyler Is this still hapenning on M-55 beta?
,
Dec 7 2016
Yes http://100.96.48.80/afe/#tab_id=view_job&object_id=745
,
Dec 7 2016
,
Dec 7 2016
,
Dec 8 2016
I've seen this before. I don't think this is blocking. used to be we have the "duration" is not long enough so the test timeout prematurely. but i think that has been fixed by Gwendal a few months before. so it it will be good to know why these are still failing. Gwendal, i'm seeing "unexpected indent regression, aborting" in the log. any idea why? 11/21 19:52:42.307 ERROR| logging_manager:0626| 11/21 19:52:42.308 ERROR| logging_manager:0626| 11/21 19:52:42.308 ERROR| logging_manager:0626| STATUS: START ---- ---- timestamp=1479786207 localtime=Nov 21 19:43:27 11/21 19:52:42.309 ERROR| logging_manager:0626| 11/21 19:52:42.309 ERROR| logging_manager:0626| STATUS: GOOD ---- sysinfo.before timestamp=1479786207 localtime=Nov 21 19:43:27 11/21 19:52:42.309 ERROR| logging_manager:0626| 11/21 19:52:42.310 ERROR| logging_manager:0626| STATUS: END GOOD ---- ---- timestamp=1479786207 localtime=Nov 21 19:43:27 11/21 19:52:42.310 ERROR| logging_manager:0626| 11/21 19:52:42.310 ERROR| logging_manager:0626| STATUS: START ---- ---- timestamp=1479786211 localtime=Nov 21 19:43:31 11/21 19:52:42.311 ERROR| logging_manager:0626| 11/21 19:52:42.311 ERROR| logging_manager:0626| STATUS: GOOD ---- sysinfo.iteration.before timestamp=1479786211 localtime=Nov 21 19:43:31 11/21 19:52:42.312 ERROR| logging_manager:0626| 11/21 19:52:42.312 ERROR| logging_manager:0626| STATUS: END GOOD ---- ---- timestamp=1479786211 localtime=Nov 21 19:43:31 11/21 19:52:42.312 ERROR| logging_manager:0626| 11/21 19:52:42.313 ERROR| logging_manager:0626| STATUS: INFO ---- ---- Job aborted by autotest_system on 2016-11-21 19:52:33 11/21 19:52:42.313 ERROR| logging_manager:0626| Unexpected indent regression, aborting 11/21 19:52:42.314 ERROR| logging_manager:0626| 11/21 19:52:42.314 ERROR| logging_manager:0626| STATUS: END ABORT hardware_StorageQualTrimStress.suspend hardware_StorageQualTrimStress.suspend None 11/21 19:52:42.314 ERROR| logging_manager:0626| parsing test hardware_StorageQualTrimStress.suspend hardware_StorageQualTrimStress.suspend 11/21 19:52:42.315 ERROR| logging_manager:0626| ADD: ABORT 11/21 19:52:42.315 ERROR| logging_manager:0626| Subdir: hardware_StorageQualTrimStress.suspend 11/21 19:52:42.315 ERROR| logging_manager:0626| Testname: hardware_StorageQualTrimStress.suspend 11/21 19:52:42.316 ERROR| logging_manager:0626| None 11/21 19:52:42.316 ERROR| logging_manager:0626| 11/21 19:52:42.316 ERROR| logging_manager:0626| STATUS: INFO ---- ---- Job aborted by autotest_system on 2016-11-21 19:52:33 11/21 19:52:42.316 ERROR| logging_manager:0626| parsing test ---- SERVER_JOB http://100.96.48.80/results/762-moblab/192.168.231.110/debug/autoserv.DEBUG
,
Dec 8 2016
I suspected the timeout as well and ran the tests with increased timeout and it still aborted.
,
Dec 9 2016
Tyler/Danny - I had a chat with Jean on this and it looks like the tests have been failing earlier too and they aren't important enough to be considered stable blockers. We can have the test owners investigate this failure, but please let me know know if you consider this as a launch blocker for moblab's 55 stable
,
Dec 9 2016
No this shouldn't be a stable blocker for M55. I saw this in M53 and M54 as well.
,
Dec 9 2016
I have seen other bugs that mention problems with the storage qual from moblab as well though. https://code.google.com/p/chrome-os-partner/issues/detail?id=59551
,
Dec 9 2016
#6: We are aborting in put_back_line_and_abort() due to a stack corruption (we want to unwind the stack too far). Can you append to this bug the full result directory, not only autoserv.DEBUG?
,
Dec 9 2016
re: #11, here it is: http://100.96.48.80/results/769-moblab/192.168.231.108/
,
Dec 9 2016
The problem is the duration: 250 (s), a little over 4 minutes, max runtime is 8 minutes The test has no time to settle in and is cancelled. Try a long time, at least 15 minutes (duration = 900)
,
Dec 9 2016
I scheduled a new run with a longer duration. I had to edit the control file to extend the duration though. http://100.96.48.80/afe/#tab_id=view_job&object_id=771
,
Jan 6 2017
If the problem is not a timeout, why is it not reported as such? I came here because I ran into a recent "unexpected indent regression, aborting". Is this a problem with the logging manager? I'll file a separate bug. For reference: https://uberchromegw.corp.google.com/i/chromeos/builders/stumpy-paladin/builds/27076
,
Jan 13 2018
,
Jan 13 2018
,
Jan 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by twreid@chromium.org
, Oct 7 2016Labels: Proj-Moblab