Closed Bug 580484 Opened 14 years ago Closed 13 years ago

Bad threading on test results from try server

Categories

(Release Engineering :: General, defect, P5)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sfink, Unassigned)

Details

I pushed 7b9073ebcc28 to the try server yesterday and am getting flooded with Windows 5.2 test results. I think I have > 170 total results right now, and it looks like I'm getting a complete set of test results for every Windows build slave.

Here are two example emails:

Your Try Server test (4edfbc094b95) was successfully completed on win32 on builder: WINNT 5.2 tryserver debug test mochitests-5/5.

It should be available for download at http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/sfink@mozilla.com-4edfbc094b95

Summary of test results:
TinderboxSummaryMessage: s: try-w32-slave26
mochitest-plain-5: 17770/0/19

Visit http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTry to view the full logs.

---------------------------------------------------------------

Your Try Server test (f8f9c5523fcd) was successfully completed on win32 on builder: WINNT 5.2 tryserver debug test mochitests-5/5.

It should be available for download at http://ftp.mozilla.org/pub/mozilla.org/firefox/tryserver-builds/sfink@mozilla.com-f8f9c5523fcd

Summary of test results:
TinderboxSummaryMessage: s: try-w32-slave19
mochitest-plain-5: 17770/0/19

Visit http://tinderbox.mozilla.org/showbuilds.cgi?tree=MozillaTry to view the full logs.
Oh. I just noticed that these are all for different commits. Um, never mind -- except why are they all threading together? I still have all try server threads open in tbird, and all of these winnt 5.2 builds are ending up under one thread.

I guess these build slaves got unblocked or enabled recently, and they're working through a monster backlog??
Ah. The References: and In-Reply-To: headers for all of these builds are set to "<tryserver-unknown>".
Summary: Mercy! Mercy! Getting flooded with test results → Bad threading on test results from try server
Sucks, but I think this is low priority.
Priority: -- → P5
I haven't seen this in ages, so I no longer care even if it hasn't been fixed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.