https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-10-24T11:46:37ZopenSUSE Project Management ToolopenQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5663472022-10-24T11:46:37Zph03nixfelix.niederwanger@suse.com
<ul></ul><p>This is likely a timeout issue, we might need to set a higher timeout on line 47: <code>assert_script_run 'bash -e valgrind-test.sh'</code>:</p>
<pre><code>assert_script_run('bash -e valgrind-test.sh', timeout => 300);
</code></pre> openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5663562022-10-24T11:53:26Zrfan1richard.fan@suse.com
<ul><li><strong>Assignee</strong> set to <i>rfan1</i></li></ul><p>It might have something to do with bad performance on arm workers.</p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5666262022-10-25T03:36:28Zrfan1richard.fan@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>It is not a performance issue, after printing the logs, I can see the below errors:</p>
<pre><code class="html syntaxhl" data-language="html">-valgrind --tool=memcheck --trace-children=yes ./valgrind-test 2>/dev/null
+valgrind -v --tool=memcheck --trace-children=yes ./valgrind-test
</code></pre>
<p>logs:</p>
<pre><code class="html syntaxhl" data-language="html">+ valgrind -v --tool=memcheck --trace-children=yes ./valgrind-test
==2050== Memcheck, a memory error detector
==2050== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2050== Using Valgrind-3.18.1-42b08ed5bd-20211015 and LibVEX; rerun with -h for copyright info
==2050== Command: ./valgrind-test
==2050==
--2050-- Valgrind options:
--2050-- -v
--2050-- --tool=memcheck
--2050-- --trace-children=yes
--2050-- Contents of /proc/version:
--2050-- Linux version 5.14.21-150400.24.28-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.37.20211103-150100.7.37) #1 SMP PREEMPT_DYNAMIC Mon Oct 10 15:21:12 UTC 2022 (f82da2c)
--2050--
--2050-- Arch and hwcaps: ARM64, LittleEndian, v8-atomics
--2050-- Page sizes: currently 4096, max supported 65536
--2050-- Valgrind library directory: /usr/lib/valgrind
--2050-- Reading syms from /var/tmp/valgrind-test
--2050-- Reading syms from /lib64/ld-2.31.so
--2050-- Reading syms from /usr/lib/valgrind/memcheck-arm64-linux
--2050-- object doesn't have a symbol table
--2050-- object doesn't have a dynamic symbol table
--2050-- Scheduler: using generic scheduler lock implementation.
--2050-- Reading suppressions file: /usr/lib/valgrind/default.supp
==2050== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-2050-by-root-on-susetest
==2050== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-2050-by-root-on-susetest
==2050== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-2050-by-root-on-susetest
==2050==
==2050== TO CONTROL THIS PROCESS USING vgdb (which you probably
==2050== don't want to do, unless you know exactly what you're doing,
==2050== or are doing some strange experiment):
==2050== /usr/lib/valgrind/../../bin/vgdb --pid=2050 ...command...
==2050==
==2050== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==2050== /path/to/gdb ./valgrind-test
==2050== and then give GDB the following command
==2050== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=2050
==2050== --pid is optional if only one valgrind process is running
==2050==
VEX: Mismatch detected between RDMA and atomics features.
Found: v8-atomics
Cannot continue. Good-bye
vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
</code></pre>
<p>However, I can't see the issue on my local setup, it might have something to do with the hardware configration.</p>
<pre><code class="html syntaxhl" data-language="html">My setup:
# lscpu|grep Flags
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
openQA workers:
# lscpu; echo 5GZT6-$?-
Architecture: aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: Cavium
Model name: ThunderX 88XX
Model: 1
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Stepping: 0x1
BogoMIPS: 200.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
</code></pre>
<p>Let me try to file a bug</p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5666292022-10-25T03:42:17Zrfan1richard.fan@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Blocked</i></li></ul><p><a href="https://bugzilla.suse.com/show_bug.cgi?id=1204685" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1204685</a></p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5670912022-10-25T13:49:14Zmgrifalconi
<ul></ul><p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15779" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15779</a> removes the test for now. Since it never worked on 15-sp4.</p>
<p>Before adding it back and to further debug, we should test it in a development job group</p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5670942022-10-25T13:50:42Zapappas
<ul><li><strong>Tags</strong> changed from <i>bugbusters</i> to <i>bugbusters, qe-core-coverage</i></li></ul> openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5707962022-11-04T09:34:53Zrfan1richard.fan@suse.com
<ul></ul><p>The bug is fixed, I will try to re-test it.</p>
<p>However the parent job is failed due to <a href="https://bugzilla.suse.com/show_bug.cgi?id=1204924" class="external">https://bugzilla.suse.com/show_bug.cgi?id=1204924</a>.</p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5806872022-12-02T09:25:16Zrfan1richard.fan@suse.com
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>In Progress</i></li></ul><p>Check if the fix is checked in: <code>http://openqa.suse.de/tests/10071023</code></p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5808762022-12-05T03:37:57Zrfan1richard.fan@suse.com
<ul></ul><p><a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16026" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16026</a></p>
openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5839062022-12-12T01:26:14Zrfan1richard.fan@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul> openQA Tests - action #119278: [qem][qe-core]test fails in valgrindhttps://progress.opensuse.org/issues/119278?journal_id=5843472022-12-13T05:43:44Zrfan1richard.fan@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>