action #55958

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

Added by SLindoMansilla 5 months ago. Updated 1 day ago.

Status:FeedbackStart date:26/08/2019
Priority:NormalDue date:
Assignee:jorauch% Done:


Category:Enhancement to existing testsEstimated time:42.00 hours
Target version:SUSE QA tests - Milestone 30



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:
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


Fails since Build 0161

Expected result

Last good: 0158

Further details

Always latest result in this scenario: latest

Related issues

Duplicated by openQA Tests - action #55520: [aarch64] test fails in soundtouch Rejected 14/08/2019
Duplicated by openQA Tests - action #57275: test fails in soundtouch Rejected 24/09/2019


#1 Updated by SLindoMansilla 4 months ago

  • Assignee set to dheidler

Please, add more information

#2 Updated by dheidler 4 months 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.


  • Try something different than aplay (eg mpv)
  • Use hda driver insted of ac97 (
  • 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

#3 Updated by dheidler 4 months ago

  • Duplicated by action #55520: [aarch64] test fails in soundtouch added

#4 Updated by SLindoMansilla 4 months ago

#6 Updated by okurz 3 months 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

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

#7 Updated by szarate 2 months ago

  • Assignee deleted (dheidler)

#8 Updated by SLindoMansilla about 1 month 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

#9 Updated by jorauch about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to jorauch

#10 Updated by mgriessmeier 14 days ago

  • Target version changed from Milestone 28 to Milestone 30

to be discussed offline next week

#11 Updated by jorauch 4 days ago

  • Status changed from In Progress to Feedback

#12 Updated by jorauch 1 day ago

PR merged, waiting for verificaiton on production

Also available in: Atom PDF