Closed Bug 359347 Opened 19 years ago Closed 19 years ago

many builds not reporting to tinderbox

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dbaron, Assigned: justdave)

References

Details

Since the tinderbox server upgrade, many builds are not reporting. See: http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey - of the 5 builds, only lhasa and nye have reported anything since 7:24pm http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox - argo-vm (twice), prometheus-vm, and bl-bldxp01 are not reporting I've closed the tree because of this.
Assigning to Dave, he has been working on webtools.
Assignee: server-ops → justdave
Dave and Justin improved something just after 23:00 PST, by fixing the fact that the firewall was blocking connections from the build lab to the new tinderbox server. Waiting to see how much that improves things (presumably the email backlog from that is being processed -- tinderbox seems quite slow now).
Assigning to the correct Dave for the job.
Assignee: justdave → justdave
OS: Other → All
Tinderbox now hasn't updated at all since 1:15 PST or so.
Dave fixed the updating problem around 9am PST. It still seems that the machines in the build lab at the office can't send email to tinderbox (presumably dm-mail01 and dm-mail02, port 25).
The key machines have now been fixed, and I've reopened the tree, but there are probably some additional machines that have fallen off that we should make an effort to look for...
Severity: blocker → major
I think the main issues here have been fixed. If you identify any more specific boxes still missing, please file individual or batch bugs.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
The NSS tinderbox is not working, I filed bug 359702.
Blocks: 359702
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.