action #14824
closedyast2_i test finishes with invalid characters
100%
Description
yast2_i test finishes with command prompt ^[f# instead of #
Updated by okurz over 7 years ago
- Description updated (diff)
- Priority changed from Normal to High
Updated by zluo over 7 years ago
Due to Bug 1012564 it is not possible to verify the issue against current build. The last successful test for yast2_i was 4 days ago.
Updated by zluo over 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 100
fixed now.
Please see reference test:
Updated by okurz over 7 years ago
we should be careful not to call it "fixed" as I am pretty sure no one changed something to get rid of the invalid character. It's just not showing up right now because of unknown reason.
Updated by asmorodskyi over 7 years ago
- Status changed from Resolved to In Progress
- Assignee deleted (
zluo)
okurz was right issue reproduces again .
Latest reproduce of the issue : https://openqa.suse.de/tests/654598#step/yast2_i/14
Latest absolute link : https://openqa.suse.de/tests/latest?distri=sle&arch=x86_64&flavor=Server-DVD&machine=64bit&version=12-SP3&test=allpatterns
Updated by zluo over 7 years ago
the latest run shows correct behavior:
Updated by asmorodskyi about 7 years ago
fresh example of a bug : https://openqa.suse.de/tests/767916#step/yast2_i/10
Updated by okurz about 7 years ago
- Status changed from In Progress to Resolved
- Assignee set to dzedro
with 23b5015 the check for correct prompt after finishing does not apply anymore.
Verified working in
https://openqa.suse.de/tests/809017#step/yast2_i/13