action #124694
closed
Redundant email about new comment in OBS
Added by livdywan about 1 year ago.
Updated about 1 year ago.
Category:
Feature requests
Description
Observation¶
For example an email like this one
Visit https://build.opensuse.org/project/show/devel:openQA
Oliver Kurz wrote in project devel:openQA:
openQA-in-openQA test(s) failed (job IDs: 3120792), see https://openqa.opensuse.org/tests/overview?version=Tumbleweed&groupid=24
Interestingly https://openqa.opensuse.org/tests/3120792#comments shows that it has an issue associated with it. Otherwise it would have also caused an "unreviewed issue" email.
In this case there's only one email, but the email is arguably irrelevant since the issue already covers it.
In other cases two emails are sent for the same job.
Acceptance criteria¶
Suggestions¶
- Copied from action #124212: Unreviewed issue for "obvious" needle mismatch without any indication what unknown error was found size:M added
- Tags set to reactive work
- Category changed from Regressions/Crashes to Feature requests
- Target version set to Ready
- Priority changed from High to Urgent
As some are already suffering from alert fatigue due to too many emails the urgency at least needs to be addressed. That could be done by temporarily disabling the openQA-in-openQA tests, commenting out the email sending in scripts or whatever, until the real issue could be addressed.
- Status changed from New to Feedback
- Assignee set to mkittler
Looks like those OBS comments are created by monitor-openqa_job. They seem rather redundant now as we now have the hook script and mails for unreviewed test failures. So I tend to remove the code for sending those comments completely.
Note that the code itself deals with the problem of creating tons of comments quite nicely by always removing existing comments. However, this doesn't help with the mail notifications.
So I propose https://github.com/os-autoinst/scripts/pull/219 to address this issue. Maybe you don't like this as a permanent solution but it at least helps to take out the urgency of the issue.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF