https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-03-25T14:12:50ZopenSUSE Project Management Toolqe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5047792022-03-25T14:12:50ZJRivrainjrivrain@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Tests</i> to <i>qe-yam</i></li><li><strong>Category</strong> deleted (<del><i>Bugs in existing tests</i></del>)</li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5047822022-03-25T14:13:02ZJRivrainjrivrain@suse.com
<ul><li><strong>Tags</strong> set to <i>qe-yast-refinement</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5063572022-03-30T08:21:32ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Target version</strong> set to <i>Current</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5064202022-03-30T09:06:14ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Tags</strong> deleted (<del><i>qe-yast-refinement</i></del>)</li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/506420/diff?detail_id=478697">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5067802022-03-31T08:24:39Zrainerkoenig
<ul></ul><p>This issue should be fixed after applying QEMURAM=4096 for <a href="https://progress.opensuse.org/issues/107326" class="external">poo#107326</a>.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5068762022-03-31T09:39:48ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>Feedback</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5068792022-03-31T09:40:44ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Assignee</strong> set to <i>rainerkoenig</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5068852022-03-31T09:40:56ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-4 priority-default closed" href="/issues/107326">action #107326</a>: command `dig www.opensuse.org +short` fails in yast_dns_server only in aarch64</i> added</li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5096762022-04-08T13:41:42ZJRivrainjrivrain@suse.com
<ul></ul><p>Happened again in last build</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5100792022-04-11T06:25:31ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>rainerkoenig</i></del>)</li></ul><p>Let's move it back to backlog as it might require different approach.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5172972022-05-09T23:59:27Zopenqa_reviewopenqa-review@suse.de
<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: yast2_cmd<br>
<a href="https://openqa.suse.de/tests/8685672#step/yast_users/1" class="external">https://openqa.suse.de/tests/8685672#step/yast_users/1</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" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 40 days if nothing changes in this ticket.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5335702022-07-05T00:16:29Zopenqa_reviewopenqa-review@suse.de
<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: yast2_cmd<br>
<a href="https://openqa.suse.de/tests/8762244#step/yast_users/1" class="external">https://openqa.suse.de/tests/8762244#step/yast_users/1</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" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5383362022-07-19T06:51:07Zhjluohluo@suse.com
<ul><li><strong>Assignee</strong> set to <i>hjluo</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5383632022-07-19T07:16:27Zhjluohluo@suse.com
<ul></ul><p>Now the original job was removed. <a href="https://openqa.suse.de/tests/8293653" class="external">https://openqa.suse.de/tests/8293653</a> </p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5388162022-07-20T07:34:25Zhjluohluo@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5389692022-07-20T08:52:21ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Workable</i></li><li><strong>Assignee</strong> deleted (<del><i>hjluo</i></del>)</li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5430412022-08-04T00:13:04Zopenqa_reviewopenqa-review@suse.de
<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: yast2_cmd<br>
<a href="https://openqa.suse.de/tests/8762244#step/yast_users/1" class="external">https://openqa.suse.de/tests/8762244#step/yast_users/1</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" or "EOL" (End-of-Life)</li>
<li>The bugref in the openQA scenario is removed or replaced, e.g. <code>label:wontfix:boo1234</code></li>
</ol>
<p>Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5628012022-10-13T06:33:19Zrainerkoenig
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>rainerkoenig</i></li></ul> qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5686002022-10-31T12:53:39ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>could you please describe the current situation?<br>
as you noticed this ticket didn't pass by refinement and as expected 18 days later there is no actual result.<br>
we should resolve it as investigation ticket and file another one with low prio with findings to check in the future.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5719722022-11-08T11:00:36ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>could you please link the ticket with the finding and resolve this one? thx.</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5725752022-11-09T13:16:54Zrainerkoenig
<ul></ul><a name="Status-of-investigation"></a>
<h3 >Status of investigation<a href="#Status-of-investigation" class="wiki-anchor">¶</a></h3>
<ul>
<li>Problem occurs sproadically, even after setting higher QEMURAM and patching the test, so that a real timeout is provided that then could be prolonged by TIMEOUT_SCALE setting.</li>
<li>In Build 38.1 we now see this sporadic issue also <a href="https://openqa.suse.de/tests/9873892#step/yast_users/7" class="external">on x86_64 architecture</a>.</li>
</ul>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5728332022-11-10T07:08:56ZJERiveraMoyajeriveramoya@suse.com
<ul></ul><p>could you please label that job in development with a new ticket where you put this investigation and resolve this one?</p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5728422022-11-10T07:41:52Zrainerkoenig
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>Further investigation of this issue is done in <a class="issue tracker-4 status-6 priority-3 priority-lowest closed" title="action: Investigate sporadic failures in yast_users test module (Rejected)" href="https://progress.opensuse.org/issues/120223">#120223</a>. </p>
qe-yam - action #108995: test fails in yast_users- timeouthttps://progress.opensuse.org/issues/108995?journal_id=5845212022-12-13T10:38:35ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Parent task</strong> set to <i>#121876</i></li></ul>