action #92764
closed
Possible spam from check_for_unsent_reports.sh, repeated sending of "PASSED" and "FAILED" emails
Added by jbaier_cz almost 3 years ago.
Updated almost 3 years ago.
Category:
Regressions/Crashes
Description
Quick notes from the conversation:
Not sure if it's useful but the Testreport resent are from already released maintenance incidents
As example
From: qa-maintenance@suse.de
To: qa-maintenance-reports@suse.de
Cc: maint-coord@suse.de
Subject: double-conversion, libqt5-qtdeclarative, libqt5-qttools, llvm7,
SUSE:Maintenance:19402:240869
X-QA-Maintenance: testreport for maintenance update
SUSE:Maintenance:19402:240869
It might be related to one fix though, some post-commit hook is probably not running correctly as some part of templates was not indexed inside search tool; so those mails might be in fact just delayed mails from the past. Although, the fix was done circa around 2pm, first reported e-mail is from 17:42. Cron job runs 4 times per hour.
Cronjob has been temporary disabled to prevent more mails from flooding your inbox. More investigation needed.
- Related to action #92755: Investigate problems with post-commit hook for testreports added
just a small note.
the resent emails were also from the FAILED testreports, not only from the PASSED.
This is an example from the FAILED:
From: qa-maintenance@suse.de
To: qa-maintenance-reports@suse.de
Cc: maint-coord@suse.de,prjmgr@suse.de
Subject: FAILED: bind, SUSE:Maintenance:19428:240376
X-QA-Maintenance: testreport for maintenance update
SUSE:Maintenance:19428:240376
- Subject changed from Possible spam from check_for_unsent_reports.sh, repeated sending of "PASSED" emails to Possible spam from check_for_unsent_reports.sh, repeated sending of "PASSED" and "FAILED" emails
- Status changed from New to Resolved
The issue has been identified. The main problem was in the sending script not being able to mark the report as sent after sending the mail. The problem was corrected on the affected reports and additionally a protection before reoccurring has been added.
I also reenabled the cron job and consider this problem solved. Please let me know if the problem persists.
jbaier_cz wrote:
I also reenabled the cron job and consider this problem solved. Please let me know if the problem persists.
Thanks a lot for taking care :)
For the moment the test report sent are looking fine and with no duplicated messages. I'll keep an eye on it.
Also available in: Atom
PDF