Need an automated way to collect failed Thunderbird 2 or 3 results on Litmus

RESOLVED FIXED

Status

Webtools Graveyard
Litmus
P2
normal
RESOLVED FIXED
10 years ago
a year ago

People

(Reporter: gkw, Assigned: coop)

Tracking

Details

(Reporter)

Description

10 years ago
Post IRC conversation, we would need an automated way to collect failed Thunderbird 2 or 3 results on Litmus.
Priority: -- → P3
(Assignee)

Updated

10 years ago
Assignee: nobody → ccooper
(Assignee)

Comment 1

10 years ago
Who wants to receive these reports (email addresses)? I can clone the existing Firefox daily reporting script for Thunderbird and start it running.
Status: NEW → ASSIGNED
Priority: P3 → P2
(Reporter)

Comment 2

10 years ago
Can the receivers' email addresses be changed easily? I can receive them now for the moment.

Wayne, interested?

Comment 3

10 years ago
presently hard to imagine myself taking it on.  
maybe wayne woods (w.woods) or tuukka (sp3000)?
do calendar ppl have litmus experience?
(Assignee)

Comment 4

10 years ago
The list of addresses resides on the server at present, so no, there's no "easy" way besides contacting a litmus server admin.
(Reporter)

Comment 5

10 years ago
We'll confirm again once MoMo has a permanent QA folk, since I can only do this as a stop gap measure.
(Assignee)

Comment 6

10 years ago
Gary: you're signed up to receive a daily report about Thunderbird results now. I'll note that Thunderbird has less traffic than Firefox, so some days there may be no report. I'll also note that the default report that the MozQA team received daily also still includes Thunderbird results.

I've also filed bug 435264 to get this report config information into the database to allow product admins to have more control over how these reports are generated and who they get sent to.

If you need to change who gets the report in the interim, just ping me and I'll change the list of recipients.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.