https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-06-23T13:51:21ZopenSUSE Project Management ToolQA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197072021-06-23T13:51:21Zgeorggkioulis@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/419707/diff?detail_id=398413">diff</a>)</li></ul> QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197102021-06-23T13:53:07Zokurzokurz@suse.com
<ul><li><strong>Project</strong> changed from <i>openQA Project</i> to <i>QA</i></li><li><strong>Subject</strong> changed from <i>Template Generator: Communicate reduced visibility of openQA incident related coverage in log</i> to <i>[tools][teregen] Template Generator: Communicate reduced visibility of openQA incident related coverage in log</i></li><li><strong>Category</strong> deleted (<del><i>Feature requests</i></del>)</li><li><strong>Target version</strong> set to <i>future</i></li></ul><p>I like the suggestion but this means we would rely on the data on smelt being present at a later time when the generated report just references that.</p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/29611">@jbaier_cz</a> do you think we could simply not have the (partially duplicate) information in the report but reference the smelt comment tab?</p>
QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197762021-06-23T15:33:22Zjbaier_czjbaier@suse.cz
<ul></ul><p>Sorry, no can do here. This issue is not relevant to the template generator at all.</p>
<p>The section 'Results from openQA incidents jobs:' is added by <a href="https://gitlab.suse.de/qa-maintenance/mtui/-/blob/master/mtui/connector/openqa/standard.py#L36" class="external">mtui</a> when the tester runs an <code>export</code> command, so the data inside the log are accurate to the time the tester actually does the test.</p>
QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197792021-06-23T15:40:21Zgeorggkioulis@suse.com
<ul></ul><p>jbaier_cz wrote:</p>
<blockquote>
<p>Sorry, no can do here. This issue is not relevant to the template generator at all.</p>
<p>The section 'Results from openQA incidents jobs:' is added by <a href="https://gitlab.suse.de/qa-maintenance/mtui/-/blob/master/mtui/connector/openqa/standard.py#L36" class="external">mtui</a> when the tester runs an <code>export</code> command, so the data inside the log are accurate to the time the tester actually does the test.</p>
</blockquote>
<p>Sorry for the mislabeling, so this issue should be mtui related.</p>
QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197822021-06-23T15:41:06Zgeorggkioulis@suse.com
<ul><li><strong>Subject</strong> changed from <i>[tools][teregen] Template Generator: Communicate reduced visibility of openQA incident related coverage in log</i> to <i>[tools][teregen] mtui: Communicate reduced visibility of openQA incident related coverage in log</i></li></ul> QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4197882021-06-23T15:46:35Zokurzokurz@suse.com
<ul></ul><p>jbaier_cz wrote:</p>
<blockquote>
<p>Sorry, no can do here. This issue is not relevant to the template generator at all.</p>
<p>The section 'Results from openQA incidents jobs:' is added by <a href="https://gitlab.suse.de/qa-maintenance/mtui/-/blob/master/mtui/connector/openqa/standard.py#L36" class="external">mtui</a> when the tester runs an <code>export</code> command, so the data inside the log are accurate to the time the tester actually does the test.</p>
</blockquote>
<p>I see. But still, do you think we could simply not have the (partially duplicate) information in the report but reference the smelt comment tab in what mtui generates?</p>
QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=4371412021-08-20T10:47:20Zjbaier_czjbaier@suse.cz
<ul><li><strong>Subject</strong> changed from <i>[tools][teregen] mtui: Communicate reduced visibility of openQA incident related coverage in log</i> to <i>[tools][mtui] Communicate reduced visibility of openQA incident related coverage in log</i></li></ul><p>I don't think plain references to external sites are good idea (specifically for test reports). Two reasons:</p>
<ol>
<li>there are things like <a href="https://progress.opensuse.org/issues/97121" class="external">https://progress.opensuse.org/issues/97121</a> which might render the link useless for some reports</li>
<li>I always though about reports as a snapshot, so they should include all information from the time the tester did the evaluation</li>
</ol>
<p>My proposal would be to continue with <a href="https://progress.opensuse.org/issues/94480" class="external">https://progress.opensuse.org/issues/94480</a> and for example put those possible duplicates into a separate file and link to the file (and add a hint with link to external site for up-to-date info?) inside the main log.</p>
QA - action #94600: [tools][mtui] Communicate reduced visibility of openQA incident related coverage in loghttps://progress.opensuse.org/issues/94600?journal_id=6018772023-02-14T16:05:34Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-4 priority-default child" href="/issues/124473">action #124473</a>: [tools] Automatic regression tests export from openQA</i> added</li></ul>