If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Tinderbox] New Build Added and Build Drop Messages should have which tree at the beginning.

VERIFIED FIXED in 2.6

Status

Webtools
Mozbot
P2
minor
VERIFIED FIXED
9 years ago
8 years ago

People

(Reporter: wolf, Assigned: wolf)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

9 years ago
The new build added and build drop messages are not consistent with the state change messages as they don't have the tree at the beginning, this makes scanning a list of reports at once, hard. Particularly if a channel has multiple large trees being reported to it. (Firefox 3.0, 3.1 and Trunk, come to mind.)
(Assignee)

Comment 1

9 years ago
Created attachment 354270 [details] [diff] [review]
Fix tinderbox messages to be more consistent.

Previously:
New build added to Firefox: WINNT 5.1 talos mozilla-central qm-pxp-trunk02 (status: Success).
Build 'MacOSX 10.4 comm-central-calendar ltn nightly' has dropped from the 'Sunbird' tinderbox.
Firefox: 'WINNT 5.1 talos mozilla-central qm-pxp-trunk01' has changed state from Test Failed to Success.

Now:
Firefox: Build 'WINNT 7.0 mozilla-central build' added to tinderbox. (Status: Burning).
Firefox: Build 'WINNT 5.1 talos mozilla-central nochrome qm-pxp-trunk07' has dropped from tinderbox.
Firefox: 'WINNT 5.2 mozilla-central build' has changed state from Success to Burning.

I left the 'Build' for the add/drop notices just to make it quick to filter them out at a glance (and it reads a little better that way.)
Assignee: nobody → bugtrap
Status: NEW → ASSIGNED
(Assignee)

Updated

9 years ago
Priority: -- → P2
(Assignee)

Comment 2

9 years ago
Checking in BotModules/Tinderbox.bm;
/cvsroot/mozilla/webtools/mozbot/BotModules/Tinderbox.bm,v  <--  Tinderbox.bm
new revision: 2.8; previous revision: 2.7
done
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Verified Fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.