Project

General

Profile

Actions

action #55958

closed

[functional][u] test fails in soundtouch - This is a product bug that may be workarounded like with aplay

Added by SLindoMansilla over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA - Milestone 30
Start date:
2019-08-26
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

There is a known sporadic bug that will not have a fix upstream nor withing SUSE.
A workaround were used to soft-failed the test: https://openqa.suse.de/tests/3289105#step/aplay/22
In this case the test failing is soundtouch, which will probably share the same destiny.

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

Reproducible

Fails since Build 0161

Expected result

Last good: 0158

Further details

Always latest result in this scenario: latest


Related issues 2 (0 open2 closed)

Has duplicate openQA Tests - action #55520: [aarch64] test fails in soundtouchRejected2019-08-14

Actions
Has duplicate openQA Tests - action #57275: test fails in soundtouchRejected2019-09-24

Actions
Actions #1

Updated by SLindoMansilla over 4 years ago

  • Assignee set to dheidler

Please, add more information

Actions #2

Updated by dheidler over 4 years ago

It seems that already the aplay test failed on aarch64 as the output audio has a too low pitch there and won't be recognized by a DTMF decoder.
But it has a false-positive needle that will make that test module still work.

Suggestions:

  • Try something different than aplay (eg mpv)
  • Use hda driver insted of ac97 (https://github.com/os-autoinst/os-autoinst/pull/1211)
  • Use multiple match areas in the for soundtouch to at least handle the time difference that aplay needs to load the next file
  • Add a workaround needle
Actions #3

Updated by dheidler over 4 years ago

  • Has duplicate action #55520: [aarch64] test fails in soundtouch added
Actions #4

Updated by SLindoMansilla over 4 years ago

Actions #6

Updated by okurz over 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_in_textmode
https://openqa.suse.de/tests/3452636

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions #7

Updated by szarate over 4 years ago

  • Assignee deleted (dheidler)
Actions #8

Updated by SLindoMansilla over 4 years ago

  • Status changed from New to Workable
  • Priority changed from High to Normal
  • Target version set to Milestone 28
  • Estimated time set to 42.00 h
Actions #9

Updated by jorauch over 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jorauch
Actions #10

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 28 to Milestone 30

to be discussed offline next week

Actions #11

Updated by jorauch over 4 years ago

  • Status changed from In Progress to Feedback
Actions #12

Updated by jorauch over 4 years ago

PR merged, waiting for verificaiton on production

Actions #13

Updated by jorauch about 4 years ago

  • Status changed from Feedback to Resolved

No Problems in production, closing this

Actions

Also available in: Atom PDF