Closed Bug 658036 Opened 13 years ago Closed 13 years ago

Duplicate emails in bulk compatibility check notification

Categories

(addons.mozilla.org Graveyard :: Admin/Editor Tools, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: krupa.mozbugs, Assigned: kumar)

References

()

Details

Attachments

(3 files)

Attached image screenshot
steps to reproduce:
1. Load https://addons.allizom.org/z/en-US/admin/validation
2. Click on 'Download Email log'
3. In the downloaded csv file. search for 'Wappalyzer'


observed behavior:
The same owner of the add-ons 'Wappalyzer' is being emailed 5 times. This add-on is fully reviewed and has no versions which are awaiting review (https://addons.allizom.org/en-US/developers/addon/wappalyzer/versions/)
There are two errors at play:

1. Two emails are getting sent for the same validation result.  This seems to be specific to the wappalyzer addon and perhaps is either related to the SQL query that starts validation or the query that selects authors to email.

2. The same author is getting emailed for each version that does not pass the compatibility test.  This is to be expected with the current behavior of validating not only the public version but any version that may be pending review.  Is it ok to send dupe emails like that?
(In reply to comment #1)
> 2. The same author is getting emailed for each version that does not pass
> the compatibility test.  This is to be expected with the current behavior of
> validating not only the public version but any version that may be pending
> review.  Is it ok to send dupe emails like that?

This isn't a blocker but it would be nice if we could somehow put the version number in the email so they realize which version we bumped.
The first email log seems to be an anomaly.  The latest email logs still have duplicate emails but they are unique per version.  This will be fixed when we only validate the latest version (bug 658173)
Depends on: 658173
(In reply to comment #2)
> This isn't a blocker but it would be nice if we could somehow put the
> version number in the email so they realize which version we bumped.

I added the addon version number to the email subject in https://github.com/jbalogh/zamboni/commit/f055302
Owners of platform-specific files will get emailed multiple times. The content of the email doesn't specify that the tests are run for individual files in a version. Is this something that we care about?
(In reply to comment #5)
> Owners of platform-specific files will get emailed multiple times.

This only happens for failure emails.  They get one email per file that failed validation.  Success emails are only sent one per version.
https://github.com/jbalogh/zamboni/commit/b31b05ff1f7102b28117c6b6423239f98c636cab
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
bug 658288 (fix to compatibility type) also fixes this bug.
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Attached image screenshot
I still see duplicate email notification in run #18

LastPass Password Manager's owner is being emailed twice.
Also, the add-on "LastPass Password manager" doesn't have  a beta or newer version awaiting review. See https://addons-next.allizom.org/en-US/developers/addon/lastpass-password-manager/versions/
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---
Target Milestone: 6.0.10 → 6.0.12
(In reply to comment #9)
> Created attachment 537832 [details]
> screenshot
> 
> I still see duplicate email notification in run #18
> 
> LastPass Password Manager's owner is being emailed twice.

Looks like they are getting an email for each platform.  In theory there could be different results.  We should specify platform in the email if it's not ALL.
Target Milestone: 6.0.12 → 6.1.2
Priority: -- → P2
Fixed in https://github.com/jbalogh/zamboni/commit/14815e9b75c1274d24daeb969042cc0f85f36b72

The failure emails are indeed sent one per file (which might span platforms) so with this change the platform name is appended to the addon name.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
verified. See post-fix screenshot
Status: RESOLVED → VERIFIED
Attached image post-fix screenshot
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: