action #12276
closed[s390] can timeout waiting for "CMS"
0%
Description
observation¶
https://openqa.suse.de/tests/440019/modules/bootloader_s390/steps/2
steps to reproduce¶
many zVM-s390 jobs fail in bootloader_s390
for this reason. Reproduce locally by repeatedly calling a simple test which is executing bootloader_s390 until the error is observed.
problem¶
H1. REJECTED: The timeout of 20 seconds is below the timeout for switching pages in s3270 which defaults to 30 seconds causing the text to be not displayed on the current page but only on the next one which is not visible --> okurz increased timeout to 60 seconds and let it run but it failed nevertheless, e.g. see http://lord.arch/tests/890
H2. We broke expect_s3270 (regression)
suggestion¶
- first: catch this error on a higher level within tests and retry the whole s3270 stuff from the test level
- second: fix it for good in expect_s3270
further details¶
what was confusing me at first is that if a test dies, the backtrace is not recorded in autoinst-log.txt, only in the text report shown in the UI. https://github.com/os-autoinst/os-autoinst/pull/513 is trying to improve this again.
workaround¶
retrigger job
Updated by okurz about 8 years ago
- Description updated (diff)
- Assignee set to okurz
Updated by okurz about 8 years ago
- Status changed from New to In Progress
Updated by okurz about 8 years ago
PR merged, verification on lord.arch with a whole bunch of successful test runs, let's wait for some days how this behaves in production. However, the change is a workaround in the tests. A proper fix should be in the backend as there is the warning about "status line matches neither buffer_ready nor buffer_full" which is not expected. Probably also we need better tests for the backend itself, then. Let's not get confused and track the rest in #10584.
Updated by okurz about 8 years ago
- Related to action #10584: [s390] sporadic fail in bootloader_s390, e.g. downloading kernel and initrd added
Updated by okurz about 8 years ago
- Status changed from Feedback to Resolved
didn't see this for long.