action #124074
closed[qe-core] leap 15.5 valgrind-test.sh in extra_tests_in_textmode failed
0%
Description
Observation¶
Hello QE
the valgrind test started to fail in two of our test modules. Could you please look into this?
the test result didn't exactly say why.
# Test died: command 'bash -e valgrind-test.sh' failed at /usr/lib/os-autoinst/testapi.pm line 922.
testapi::assert_script_run("bash -e valgrind-test.sh") called at opensuse/tests/console/valgrind.pm line 47
valgrind::run(valgrind=HASH(0xaaab06f14998)) called at /usr/lib/os-autoinst/basetest.pm line 339
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 333
basetest::runtest(valgrind=HASH(0xaaab06f14998)) called at /usr/lib/os-autoinst/autotest.pm line 387
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 387
autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 244
eval {...} called at /usr/lib/os-autoinst/autotest.pm line 244
autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 295
autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0xaaab07592e60)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0xaaab07592e60), CODE(0xaaab08227f10)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 489
Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0xaaab07592e60)) called at /usr/lib/os-autoinst/autotest.pm line 297
autotest::start_process() called at /usr/lib/os-autoinst/OpenQA/Isotovideo/Runner.pm line 94
OpenQA::Isotovideo::Runner::start_autotest(OpenQA::Isotovideo::Runner=HASH(0xaaaaff8ad6c8)) called at /usr/bin/isotovideo line 133
openQA test in scenario opensuse-15.5-DVD-aarch64-extra_tests_in_textmode@aarch64 fails in
valgrind
Test suite description¶
Maintainer: QE Core
Mainly console extratest.
Reproducible¶
Fails since (at least) Build 388.1
Expected result¶
Last good: 372.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by lkocman about 1 year ago
- Subject changed from leap 15.5 valgrind-test.sh failed to leap 15.5 valgrind-test.sh in extra_tests_in_textmode failed
Updated by maritawerner about 1 year ago
- Subject changed from leap 15.5 valgrind-test.sh in extra_tests_in_textmode failed to [qe-core] leap 15.5 valgrind-test.sh in extra_tests_in_textmode failed
Updated by openqa_review about 1 year 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_textmode
https://openqa.opensuse.org/tests/3160103#step/valgrind/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by ggardet_arm about 1 year ago
The error is:
./valgrind-test: symbol lookup error: /usr/lib/valgrind/vgpreload_helgrind-amd64-linux.so: undefined symbol: pthread_mutexattr_gettype
or on aarch64:
./valgrind-test: symbol lookup error: /usr/lib/valgrind/vgpreload_helgrind-arm64-linux.so: undefined symbol: pthread_mutexattr_gettype
Updated by ggardet_arm about 1 year ago
- Status changed from New to Rejected