Closed
Bug 1064810
Opened 10 years ago
Closed 10 years ago
tryserver emails listing incorrect changesets
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1062557
People
(Reporter: jfkthame, Unassigned)
Details
The last couple of "thank you for your submission" emails I have received from tryserver have included the wrong list of changesets in their summary: several changesets from someone else's try push, either immediately preceding or immediately following mine, have been listed in addition to the changesets I actually pushed. I've had a number of previous "thanks" emails that correctly listed the changesets in my push, and didn't include spurious ones; did I just get lucky up till today, or has something changed/broken? Example: for https://tbpl.mozilla.org/?tree=Try&rev=5366361829a3, the message I received reads: ------------------------------- Thank you for your try submission. It's the best! Results will be displayed on TBPL as they come in: https://tbpl.mozilla.org/?tree=Try&rev=5366361829a3 Alternatively, view them on Treeherder (experimental): https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=5366361829a3 Once completed, builds and logs will be available at: https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/try-builds/jkew@mozilla.com-5366361829a3 Summary: * try: -b d -p linux64,macosx64,win32 -u * [mq]: prog.diff * Bug 687807 - Tests for stretchy MathML r=fredw * Bug 687807 - Improvements to stretching of embellished operators * try: -b do -p all -u none * [mq]: enable-woff2-support --------------------------- but in this case, I pushed only the last two of those changesets (enable-woff2-support, and the trychooser line). The others come from https://tbpl.mozilla.org/?tree=Try&rev=100612b6831e, which was pushed a few seconds later.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•