https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-04-29T07:44:20ZopenSUSE Project Management ToolopenQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2085532019-04-29T07:44:20ZXiaojing_liuxliu1@suse.com
<ul></ul><p>In overview page, there is a list of failed needles when put cursor on a failed module. There is no list shown in Soft Failed module. Does this action mean that it should show a list of somethings likes Failed modules? I do some test, and check the code, there is no needle name recorded in result json file when result status is "softfailed". Does this action mean we should write somethings in result json file in order to show detail list? if it does, what need to be recorded?</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2085922019-04-29T09:02:13Zcoolocoolo@suse.com
<ul></ul><p>No, this is something else. And I don't want that.</p>
<p>Currently workaround property is a boolean, so if a needle matched with this property, we mark the match and the test as softfailed. But the reviewer has no chance to know why. So this ticket asks to make workaround a string (with migration path treating boolean as 'unknown' I suppose).</p>
<p>Then the soft fail reason would become this string.</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2090152019-04-30T08:42:18Znicksingernsinger@suse.com
<ul></ul><p>The functional team currently uses the following test to check for proper workaround tags: <a href="https://github.com/os-autoinst/os-autoinst-needles-tests/blob/a09a78a8687059f01b1765d7af4ff1efe32e6879/test.py" class="external">https://github.com/os-autoinst/os-autoinst-needles-tests/blob/a09a78a8687059f01b1765d7af4ff1efe32e6879/test.py</a><br>
This should give you some insights what values are possible in the filename and how we're using it inside SUSE.</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2103622019-05-07T06:29:47ZXiaojing_liuxliu1@suse.com
<ul><li><strong>Assignee</strong> set to <i>Xiaojing_liu</i></li><li><strong>Target version</strong> changed from <i>Ready</i> to <i>Current Sprint</i></li></ul> openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2109442019-05-09T10:30:10ZXiaojing_liuxliu1@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2225032019-06-20T16:01:59Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>124</i> to <i>Feature requests</i></li></ul> openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2328892019-08-07T05:40:00Zokurzokurz@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/32669">@Xiaojing_liu</a> I guess after three months this ticket deserves an update :)</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2329042019-08-07T06:10:16ZXiaojing_liuxliu1@suse.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>openQA PR: <a href="https://github.com/os-autoinst/openQA/pull/2070" class="external">https://github.com/os-autoinst/openQA/pull/2070</a><br>
os-autoinst PR: <a href="https://github.com/os-autoinst/os-autoinst/pull/1153" class="external">https://github.com/os-autoinst/os-autoinst/pull/1153</a></p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2360272019-08-18T14:53:52Zokurzokurz@suse.com
<ul><li><strong>File</strong> <a href="/attachments/8432">Screenshot_20190818_162455_new_os-autoinst_old_openqa_question_mark.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/8432/Screenshot_20190818_162455_new_os-autoinst_old_openqa_question_mark.png">Screenshot_20190818_162455_new_os-autoinst_old_openqa_question_mark.png</a> added</li><li><strong>File</strong> <a href="/attachments/8429">Screenshot_20190818_162455_new_os-autoinst_old_openqa_soft_fail_needle.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/8429/Screenshot_20190818_162455_new_os-autoinst_old_openqa_soft_fail_needle.png">Screenshot_20190818_162455_new_os-autoinst_old_openqa_soft_fail_needle.png</a> added</li></ul><p>both merged and deployed to o3. Explicit calls of <code>record_soft_failure</code> look fine, I could not find any soft-failed needles right now. On OSD with the change of os-autoinst deployed I can see that <code>record_soft_failure</code> in old job results causes question marks in a 5 month old job like in</p>
<p><img src="https://progress.opensuse.org/attachments/download/8432/Screenshot_20190818_162455_new_os-autoinst_old_openqa_question_mark.png" alt="Screenshot_20190818_162455_new_os-autoinst_old_openqa_question_mark.png" loading="lazy" /></p>
<p>and still correct handling of soft-fail needles as in</p>
<p><img src="https://progress.opensuse.org/attachments/download/8429/Screenshot_20190818_162455_new_os-autoinst_old_openqa_soft_fail_needle.png" alt="Screenshot_20190818_162455_new_os-autoinst_old_openqa_soft_fail_needle.png" loading="lazy" /></p>
<p>after the corresponding openQA change deployed to osd now as well this still looks the same.</p>
<p>Next steps can be to check if results are rendered correctly after new tests have been executed anytime after now. Also I guess – reading the ticket description – the soft-failures can be propagated to the display of failed modules in both /tests/overview as well as the "next&previous" list. <a class="user active user-mention" href="https://progress.opensuse.org/users/15">@coolo</a> can you confirm that this meets what you had in mind?</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2361832019-08-19T09:16:49Zcoolocoolo@suse.com
<ul></ul><p>I can't say for sure what I had in mind, but I don't think with 'in the overview' refers to /tests/overview - but merely that it doesn't require a look at the filename of specific needles to see the problem. So if it's visible like explict record_soft_fails, we're done here.</p>
openQA Project - action #33706: Parameterize workaround propertyhttps://progress.opensuse.org/issues/33706?journal_id=2363272019-08-19T12:14:09Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>ok, so I guess I can set it to "Resolved" then</p>