Closed Bug 797929 Opened 13 years ago Closed 13 years ago

current tinderbox.m.o is incomplete (NSS and possibly others)

Categories

(Developer Services :: General, task, P1)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: KaiE, Assigned: ashish)

References

()

Details

This page is too empty: http://tinderbox.mozilla.org/showbuilds.cgi?tree=NSS It should look more like this older output: http://tinderbox.mozilla.org/showbuilds.cgi?tree=NSS&maxdate=1349327153&hours=24&legend=0&norules=1 My guess is that email routing to tinderbox is broken. Could you please have a look? Thanks in advance. Cloned bug to make sure we have the right CC list. +++ This bug was initially created as a clone of Bug #778908 +++ +++ This bug was initially created as a clone of Bug #728510 +++
Summary: current tinderbox.m.o is incomplete (NSS and possible others) → current tinderbox.m.o is incomplete (NSS and possibly others)
Assignee: server-ops → server-ops-devservices
Component: Server Operations → Server Operations: Developer Services
QA Contact: jdow → shyam
Hmm, when I filed this bug, there was only one row shown, with only 4 columnes (so only 4 yellow boxes in total). But now the page has much more information again. Maybe it was a temporary glich? I'll keep watching the page...
Assignee: server-ops-devservices → server-ops
Component: Server Operations: Developer Services → Server Operations
QA Contact: shyam → jdow
Assignee: server-ops → ashish
Component: Server Operations → Server Operations: Developer Services
QA Contact: jdow → shyam
Kicked sendmail on the server and the mail queue is slowly processing/flushing out.
(In reply to Kai Engert (:kaie) from comment #1) > Hmm, when I filed this bug, there was only one row shown, with only 4 > columnes (so only 4 yellow boxes in total). > > But now the page has much more information again. > Maybe it was a temporary glich? > > I'll keep watching the page... The underlying vmware/netapp infrastructure that tinderbox runs on had some issues this morning, given that tinderbox relies on email it probably got queued up and retried later. Kai, can you let us know if you think it is clearing up on its own or what we should look into?
Corey, thanks for the explanation. Given that the page is slowly filling with more information, it sounds like you fixed the cause of this issue. Thanks for your help. I'll resolve as fixed and reopen if necessary.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.