https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842023-02-09T10:01:38ZopenSUSE Project Management ToolopenQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6000752023-02-09T10:01:38Zlivdywanliv.dywan@suse.com
<ul><li><strong>Copied from</strong> <i><a class="issue tracker-4 status-3 priority-6 priority-high2 closed" href="/issues/124143">action #124143</a>: openqa-in-openqa test fails because text color changed - missing CSS? size:M</i> added</li></ul> openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6011902023-02-13T15:52:07Ztinitatina.mueller+trick-redmine@suse.com
<ul></ul><p>All the "Unreviewed issue" notifications I can find link to jobs where there was no bugref carryover yet.<br>
If a carryover happens then the hook script is not called, so no email should be sent.</p>
<p>The first bugref for <a href="https://openqa.opensuse.org/tests/3105735#next_previous" class="external">https://openqa.opensuse.org/tests/3105735#next_previous</a> openqa-Tumbleweed-dev-x86_64-Build:TW.17520-openqa_install+publish@64bit-2G was added a day later <a href="https://openqa.opensuse.org/tests/3106678#comments" class="external">https://openqa.opensuse.org/tests/3106678#comments</a><br>
The first bugref for <a href="https://openqa.opensuse.org/tests/3105702#next_previous" class="external">https://openqa.opensuse.org/tests/3105702#next_previous</a> openqa-Tumbleweed-dev-x86_64-Build:TW.17519-openqa_from_git@64bit-2G was added directly after that job <a href="https://openqa.opensuse.org/tests/3105734#comments" class="external">https://openqa.opensuse.org/tests/3105734#comments</a></p>
<p>So for openqa_install+publish we still got emails until the next morning until the bugref was added.<br>
Probably it was just confusing because we have different test scenarios with the same failure, and the bugref was first only added to one of the scenario.</p>
<p>Or do you have a specific notification where you think that shouldn't have been sent?</p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6011932023-02-13T15:54:10Ztinitatina.mueller+trick-redmine@suse.com
<ul></ul><blockquote>
<p>Consider explicitly treating needle mismatches as "reviewed"</p>
</blockquote>
<p>Why should a needle mismatch be treated as reviewed?</p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6012052023-02-13T16:56:50Zmkittlermarius.kittler@suse.com
<ul></ul><p>When I've seen the mail food I initially confused it with messages from logwarn. So I was wondering for what specific place in the openQA job logs these mails were generated for and why the mail is generated considering there's nothing wrong with os-autoinst or openQA themselves. But apparently it is really just about the job not having a bugref and also no ticket with auto_review regex.</p>
<p>Nevertheless it is bad to get a flood of mails for one issue (until someone is able to create at least a ticket about it).</p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6030502023-02-16T11:08:12Zlivdywanliv.dywan@suse.com
<ul><li><strong>Subject</strong> changed from <i>Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found</i> to <i>Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/603050/diff?detail_id=566066">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6032842023-02-16T16:56:49Zlivdywanliv.dywan@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-3 priority-6 priority-high2 closed" href="/issues/124694">action #124694</a>: Redundant email about new comment in OBS</i> added</li></ul> openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6048532023-02-21T12:47:56Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul><p>I've set the frequency of <a href="http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/configure" class="external">http://jenkins.qa.suse.de/job/trigger-openQA_in_openQA-TW/configure</a> to hourly (<code>H/15 …</code> -> <code>H …</code>). I think this should cover AC1. At lest the flood of mails will be reduced by a factor of 4. We can always adjust this on Jenkins-level.</p>
<p>Note that Jenkins also polls <a href="http://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed/noarch" class="external">http://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed/noarch</a> for changes (content and modification date). However, this is likely pointless because the web server doesn't return a last modified date (see <code>curl -s -v -X HEAD http://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed/noarch</code>) and the contents contain a csrf-token that is likely to change between requests.</p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6048832023-02-21T13:39:14Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>This should improve the wording for AC2: <a href="https://github.com/os-autoinst/scripts/pull/218" class="external">https://github.com/os-autoinst/scripts/pull/218</a></p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6052942023-02-22T10:45:38Ztinitatina.mueller+trick-redmine@suse.com
<ul><li><strong>File</strong> <a href="/attachments/14666">label-known-issues-improved-email.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/14666/label-known-issues-improved-email.png">label-known-issues-improved-email.png</a> added</li></ul><p>I added a screenshot of how the notification looks now</p>
openQA Project - action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:Mhttps://progress.opensuse.org/issues/124212?journal_id=6053992023-02-22T14:17:59Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>I think it is clear enough. The reduced triggering frequency is also visibly effective on <a href="https://openqa.opensuse.org/group_overview/24" class="external">https://openqa.opensuse.org/group_overview/24</a>. So I'm considering this resolved.</p>