Closed Bug 694987 Opened 14 years ago Closed 14 years ago

[birch] change the buildid to be different from the nightly to distinguish it from the nightly crashes in Socorro

Categories

(Release Engineering :: General, defect, P1)

ARM
Android
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nhirata, Unassigned)

References

Details

Please change the buildid to be different from the nightly to distinguish it from the nightly crashes in Socorro. bug 694603; bug 694566 are examples of birch crashes.
ie from nightly to birch
I think this needs someone from Releng to do this.
Component: General → Release Engineering
Depends on: 694077
Product: Fennec → mozilla.org
QA Contact: general → release
Version: Trunk → other
Naoki means the release channel, not the buildid. ;-) And actually, the release channel is already different from Nightly builds, as it's "default", just like for every self-made build or short-lived development branch. Not sure if that needs changing at all.
The channel will change to 'nightly-birch' as part of bug 694077.
OK, then this is either dependent or a dupe of bug 694077. Naoki?
catlee, won't we have 'Release Channel default' for dep builds on all branches ? ie bug 692436. That must be where the existing crash reports are coming from, given nightlies for birch android only got enabled today.
https://crash-stats.mozilla.com/topcrasher/byversion/Fennec/10.0a1/7 number 8 crasher ( mozalloc_abort | moz_xmalloc | libxul.so@0x23268a ) in the top 10 crashers is happening on birch branch.
(In reply to Nick Thomas [:nthomas] from comment #6) > catlee, won't we have 'Release Channel default' for dep builds on all > branches ? Yes, and IMHO it's good that way. Once we have "nightlies" from birch that have their own channel set, we should be good as most people should be using/testing those, I hope.
Isn't that fixed, as we report the release channel as "nightly-birch" now?
Yes, Kairo, I believe that this could be closed out as Socorro is currently showing nightly-birch now as per comment 4.
Let's mark it fixed then - the actual fix was deploying bug 694077, for the record.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.