Project

General

Profile

action #53996

[functional][u][sporadic] test fails in timezone - serial console is not reliable

Added by dheidler over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 28
Start date:
2019-07-09
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP5-Server-DVD-aarch64-extra_tests_in_textmode@aarch64 fails in
timezone

Task

  1. Run 100 jobs to see reproducibility.
  2. Put it back to be refined.

Reproducible

Fails since (at least) Build 0161

Expected result

Last good: 0158 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #58697: [kernel][tools] test fails in install_ltpResolved2019-10-25

Has duplicate openQA Tests - action #55967: [tools][u] test fails in gdb - Unstable serial terminal causes failures in different partsRejected2019-08-26

History

#1 Updated by SLindoMansilla over 2 years ago

  • Subject changed from test fails in timezone to [functional][u] test fails in timezone
  • Priority changed from Normal to High

#3 Updated by SLindoMansilla over 2 years ago

  • Subject changed from [functional][u] test fails in timezone to [functional][u][sporadic] test fails in timezone
  • Description updated (diff)
  • Assignee set to szarate
  • Priority changed from High to Normal
  • Target version set to Milestone 26

#4 Updated by szarate over 2 years ago

  • Status changed from New to In Progress

So, It's kinda easy to reproduce:

I've started digging a bit to try to figure out what's the problem... but looks like that setting the type_string to slow would already do the trick, however I remember there was a similar issue back in the day with some tests as well... Will spend the rest of the day in this and see...

#5 Updated by szarate over 2 years ago

  • Status changed from In Progress to Feedback

I've created a pull request to switch from serial_terminal to root-console instead (which I'm not really happy about), but this would reduce the reproduceability of this problem... However in any case, I will try to investigate a bit more to try and understand why this happens on aarch64. Might be load related, but still... the test runner should be able to cope with this...

#7 Updated by SLindoMansilla over 2 years ago

Is this still waiting for someone's feedback?

#8 Updated by szarate over 2 years ago

My feedback, I'll update this later today

#9 Updated by mgriessmeier over 2 years ago

  • Target version changed from Milestone 26 to Milestone 27

szarate wrote:

My feedback, I'll update this later today

"today"? ;)

#10 Updated by szarate over 2 years ago

mgriessmeier wrote:

szarate wrote:

My feedback, I'll update this later today

"today"? ;)

Today, 24 days ago xD, https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8027#issuecomment-516304483 long story short, these failures from time to time happen mostly due to the worker being under some load, and will happen again regardless of using serial console or a tty (Which is kinda worse on aarch64).

I guess we could add some time in the future to take a look at this kind of problems... Not sure if somebody from tools team would be interested into looking at it.

#11 Updated by szarate over 2 years ago

  • Subject changed from [functional][u][sporadic] test fails in timezone to [functional][u][sporadic] test fails in timezone - serial console is not reliable
  • Status changed from Feedback to Workable
  • Assignee deleted (szarate)

One option is to actually convert this test to a bash script and run it from there, after all... there's no screen matching, and no fancy things being used...

#12 Updated by SLindoMansilla over 2 years ago

  • Estimated time set to 42.00 h

#13 Updated by mgriessmeier over 2 years ago

  • Target version changed from Milestone 27 to Milestone 28

#14 Updated by szarate over 2 years ago

  • Related to action #55967: [tools][u] test fails in gdb - Unstable serial terminal causes failures in different parts added

#15 Updated by szarate about 2 years ago

  • Related to action #58697: [kernel][tools] test fails in install_ltp added

#17 Updated by szarate about 2 years ago

Now that we have that PR merged, once deployed, we can bring back the serial console, specially for aarch64

#18 Updated by szarate about 2 years ago

  • Related to deleted (action #55967: [tools][u] test fails in gdb - Unstable serial terminal causes failures in different parts)

#19 Updated by szarate about 2 years ago

  • Has duplicate action #55967: [tools][u] test fails in gdb - Unstable serial terminal causes failures in different parts added

#20 Updated by zluo about 2 years ago

  • Status changed from Workable to Rejected
  • Assignee set to zluo

https://openqa.suse.de/tests/3575790#next_previous doesn't show any issue with serial console. Suggest to close this ticket now.

Also available in: Atom PDF