action #18132
closed[tools] test fails to assert command because a wrong string was written to serial - (anti-ninja-key)
0%
Description
Observation¶
openQA test fails in scenarios sle-12-SP3-Server-DVD-ppc64le-sdk@ppc64le Build 0299 osd#840897
Failing asserting pattern after executed command.
The command typed here (search for 07:11:46.1898 91700): osd#840897/file/autoinst-log.txt
Is properly received by the machine here: osd#840897/modules/curl_https/steps/6
But the serial output differs here (search for SCRIPT_FINISHEDnw9_-0-; the original pattern SCRIPT_FINISHEDnw9e_-0- is not there): osd#840897/file/serial0.txt
Reproducible¶
Fails since (at least) Build 0299 osd#832473
Expected result¶
Last good: 0290
Further details¶
Always latest result in this scenario: latest
Files
| from os-autoinst--type to os-autoinst--wait_serial.png (18.9 KB) from os-autoinst--type to os-autoinst--wait_serial.png | Graphic help to understand why it is different from ninja keys |
Updated by SLindoMansilla about 7 years ago
- Description updated (diff)
- Category changed from Bugs in existing tests to Infrastructure
Updated by SLindoMansilla about 7 years ago
- Subject changed from [tools] test fails to assert command because a wrong string was written to serial to [tools] test fails to assert command because a wrong string was written to serial - (anti-ninja-key)
- Description updated (diff)
Updated by okurz about 7 years ago
- Related to action #17594: [tools]Missing characters in the middle of type_string/assert_script_run (Ninja Keys) added
Updated by okurz about 7 years ago
- Project changed from openQA Tests to openQA Project
- Category changed from Infrastructure to Regressions/Crashes
Updated by SLindoMansilla about 7 years ago
It also happens here: https://openqa.suse.de/tests/855023#step/zypper_in/5
Updated by coolo over 6 years ago
- Status changed from New to Closed
this is the infamous ppc qemu bug - I'm too lazy to dig it out, but it's not openQA's fault