action #17872
closed
[sles][functional] sles12_qa_acceptance_fs_stress times out after 2h with no useful information
Added by SLindoMansilla about 7 years ago.
Updated almost 7 years ago.
Category:
Bugs in existing tests
Description
observation¶
https://openqa.suse.de/tests/829634 is timing out after 2h with no useful information.
test is giving not helpful information
19:00:59.1867 16655 <<< testapi::type_string(string='while [[ ! -f /var/log/qaset/control/DONE ]]; do sleep 30; done; echo TESTRUN_FINISHED-91668 >> /dev/ttyS0', max_interval=250, wait_screen_changes=0)
19:01:06.3245 16655 <<< testapi::send_key(key='ret')
19:01:06.5357 16655 <<< testapi::wait_serial(regexp='TESTRUN_FINISHED-91668', timeout=10800)
19:17:09.2037 16659 considering VNC stalled - turning black
20:58:28.6769 16647 signalhandler got TERM - loop 1
further details¶
latest
- Assignee set to Anonymous
- Assignee changed from Anonymous to yosun
All qa_automation tests are using /usr/share/qa/qaset/bin/junit_xml_gen.py script which I can't find anywhere.
assert_script_run("/usr/share/qa/qaset/bin/junit_xml_gen.py -n 'regression' -d -o /tmp/junit.xml /var/log/qaset");
Yong Sun, could you please take over this ticket?
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
Hi Yi, actually it fails not in what it test, so the log is useless. It's fails in openQA booting part. And it runs no problem in this moment.
All three stress run in acceptance tests are based on qa_run.pm, and the structure of it is too bloated. I think the suitable description for this issue is to raise up the debug ability for "qa_run.pm". So I create a new ticket to follow it, and assigned myself to it. https://progress.opensuse.org/issues/19362
Hope you don't mind I close this one.
Next time just update the existing ticket. The subject line can be simply rewritten and such. No need to create a new ticket.
Also available in: Atom
PDF