Project

General

Profile

Actions

action #10138

closed

clear console seems to not work everytime

Added by okurz over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Bugs in existing tests
Start date:
2016-01-07
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

observation

clear console seems to not work, e.g. see


Checklist

  • SLE
  • Tumbleweed
  • Leap
Actions #1

Updated by okurz over 8 years ago

  • Priority changed from Normal to Urgent
Actions #2

Updated by RBrownSUSE over 8 years ago

  • Assignee set to RBrownSUSE
  • % Done changed from 0 to 80
Actions #3

Updated by RBrownSUSE over 8 years ago

  • Status changed from New to In Progress
Actions #4

Updated by RBrownSUSE over 8 years ago

  • Target version changed from 156 to 154
Actions #5

Updated by RBrownSUSE over 8 years ago

  • Assignee changed from RBrownSUSE to okurz

Proposed fix superseded by https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/926

Assigning to Oli

Actions #6

Updated by RBrownSUSE over 8 years ago

  • Checklist item changed from to [ ] SLE, [ ] Tumbleweed, [ ] Leap
  • Target version changed from 154 to 162
Actions #7

Updated by okurz over 8 years ago

  • Description updated (diff)
Actions #8

Updated by okurz over 8 years ago

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?

Actions #9

Updated by okurz over 8 years ago

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
Actions #10

Updated by okurz over 8 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

tests seem to be fixed regarding to 'clear-console'. Follow up task about improvement on "assert_screen" created: https://progress.opensuse.org/issues/10368

Actions #11

Updated by okurz about 8 years ago

issue mentioned in #10138#note-8 fixed in #10326

Actions #12

Updated by okurz about 8 years ago

  • Target version changed from 162 to Milestone 1
Actions

Also available in: Atom PDF