https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-10-04T13:10:25ZopenSUSE Project Management ToolopenQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2478322019-10-04T13:10:25Zapappas
<ul></ul><p>I don't think that this is a bug in the test, but a bug in openQA. The serial console is not working again, so the <code>wait_serial</code> function is failing. </p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2481832019-10-08T10:29:58Zokurzokurz@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/32354">@apappas</a> I think it simply never worked. It's unfortunate that it seems there is so little care for failing tests hence this was never detected because on s390x there is no (easy) way to revert to snapshots so the job failed for very long in <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="action: [qam] test fails in java (Resolved)" href="https://progress.opensuse.org/issues/56969">#56969</a> and never reached gdb. I do not know how this is supposed to ever work, to just start gdb and assume that string would show up on the serial port as it's never forwarded there.</p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2481892019-10-08T10:30:14Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/56969">action #56969</a>: [qam] test fails in java</i> added</li></ul> openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2482942019-10-08T16:09:11Zapappas
<ul></ul><p>I think it's best that I rewrite the test as a python script to be interpreted by gdb.<br>
It will not then be interactive and I will be able to just use assert_script_run.</p>
<p>What do you think <a class="user active user-mention" href="https://progress.opensuse.org/users/17668">@okurz</a>?</p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2483152019-10-08T16:25:32Zokurzokurz@suse.com
<ul></ul><p>Makes sense. As an alternative you might want to log all output of gdb to /dev/$serialdev which allows to still use <code>wait_serial</code>. Both approaches sound easy to me.</p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2490862019-10-11T08:06:51Zbrhavelbhavel@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul> openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2491012019-10-11T08:21:16Zcoolocoolo@suse.com
<ul></ul><p>As it's Urgent now: if you can't get this done today, please take the test out of QAM (and keep the ticket open)</p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2491882019-10-11T13:55:18Zapappas
<ul><li><strong>Subject</strong> changed from <i>[QAM] test fails in gdb </i> to <i>test fails in gdb </i></li><li><strong>Assignee</strong> deleted (<del><i>apappas</i></del>)</li></ul> openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2491942019-10-11T14:04:01Zapappas
<ul><li><strong>Subject</strong> changed from <i>test fails in gdb </i> to <i>[QAM] test fails in gdb </i></li><li><strong>Assignee</strong> set to <i>apappas</i></li><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul> openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2491972019-10-11T14:12:04Ztjyrinki_susetjyrinki+redmine@suse.de
<ul></ul><p>Passing on x86_64, and s390x already disabled currently:</p>
<p><a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191010-2&groupid=232" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191010-2&groupid=232</a></p>
<p>vs where this was linked from <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20190911-1&groupid=232" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20190911-1&groupid=232</a></p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2504572019-10-15T15:13:47Zcoolocoolo@suse.com
<ul></ul><p>Your link is misleading as it 10-2 wasn't tested for s390x (for whatever reason): <a href="https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191013-1&groupid=232" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=15-SP1&build=20191013-1&groupid=232</a> fails</p>
<p>I worked around it now by setting EXCLUDE_MODULES=gdb. So please fix and validate with care :)</p>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2564812019-11-12T06:59:39Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: extra_tests_in_textmode<br>
<a href="https://openqa.suse.de/tests/3575790" class="external">https://openqa.suse.de/tests/3575790</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released"</li>
<li>The label in the openQA scenario is removed</li>
</ol>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2596702019-11-26T07:01:45Zokurzokurz@suse.com
<ul></ul><p>This is an autogenerated message for openQA integration by the openqa_review script:</p>
<p>This bug is still referenced in a failing openQA test: extra_tests_in_textmode<br>
<a href="https://openqa.suse.de/tests/3575790" class="external">https://openqa.suse.de/tests/3575790</a></p>
<p>To prevent further reminder comments one of the following options should be followed:</p>
<ol>
<li>The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted</li>
<li>The openQA job group is moved to "Released"</li>
<li>The label in the openQA scenario is removed</li>
</ol>
openQA Tests - action #57698: [QAM] test fails in gdb https://progress.opensuse.org/issues/57698?journal_id=2740072020-01-23T15:52:26Zapappas
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Fixed with this PR <a href="https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8709" class="external">https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8709</a></p>