action #10138
closed
clear console seems to not work everytime
Added by okurz almost 9 years ago.
Updated almost 9 years ago.
Category:
Bugs in existing tests
Description
observation¶
clear console seems to not work, e.g. see
- Priority changed from Normal to Urgent
- Assignee set to RBrownSUSE
- % Done changed from 0 to 80
- Status changed from New to In Progress
- Target version changed from 156 to 154
- Assignee changed from RBrownSUSE to okurz
- Checklist item changed from to [ ] SLE, [ ] Tumbleweed, [ ] Leap
- Target version changed from 154 to 162
- Description updated (diff)
My PR got merged but I don't understand what is happening here:
>>> assert_screen: match=broken-console-font timed out after 5
<<< type_string(string='clear
', max_interval=250)
<<< assert_screen(mustmatch='cleared-console', timeout=30)
MATCH(consoletest_setup-20141125:0.96)
MATCH(cleared-console-autoyast-font-20141126:0.96)
no match 30
MATCH(consoletest_setup-20141125:1.00)
MATCH(cleared-console-autoyast-font-20141126:1.00)
>>> assert_screen: match=cleared-console timed out after 30
<<< mydie(cause_of_death=[
'needle(s) \'cleared-console\' not found'
])
After the call to "clear" there is
no match 30
which means that there was no match but we still have a timeout of "30 tries". correct?
why don't I see a decrease to 0 before failing then?
ok, I think I understood it better.
no match <high_number>
could mean it exited early from the loop because the screen did not change at all --> check in source code and try to improve log message
no match 2
and then fail could mean an "off-by-one" incorrectness, return from the loop in the second-to-last run not the last run --> crosscheck and potentially improve
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
- Target version changed from 162 to Milestone 1
Also available in: Atom
PDF