Closed Bug 738354 (talos-r3-xp-057) Opened 12 years ago Closed 11 years ago

talos-r3-xp-057 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
Windows XP
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslave][capacity][decommission?])

      No description provided.
Depends on: 738355
Needs some post-reimage love, it fails to talk to the opsi server.
Whiteboard: [buildduty]
slave had wrong host-key. I regenerated it and rebooted, and it's now connected to buildbot.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whatever it had that called for the reimage doesn't appear to have been cured - https://tbpl.mozilla.org/php/getParsedLog.php?id=12566687&tree=Mozilla-Inbound is the one I have in front of me, but https://secure.pub.build.mozilla.org/buildapi/recent/talos-r3-xp-057 says it's mostly failing.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Interesting, https://tbpl.mozilla.org/php/getParsedLog.php?id=12567538&tree=Mozilla-Aurora is that same unknown set of dozens of failures, but on Aurora.
disabled in slavealloc per philor's request
Let's re-image once more and put it through staging.

A lot of NS_ERROR_FILE_ACCESS_DENIED lines in there.

It seems that it was the xpcshell jobs and the mochitest ones that failed.
I will run a full disk check to see if it finds anything.
This scanning is being done at start-up. I will check tomorrow (if I don't forget).
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #8)
> This scanning is being done at start-up. I will check tomorrow (if I don't
> forget).

ping?
Nevermind, this slaves seems to be back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
That boy ain't right - the two I have in front of me, https://tbpl.mozilla.org/php/getParsedLog.php?id=13415689&tree=Mozilla-Inbound and https://tbpl.mozilla.org/php/getParsedLog.php?id=13413048&tree=Firefox, are startup hangs, but https://secure.pub.build.mozilla.org/buildapi/recent/talos-r3-xp-057 makes it look like it might manage some other flavors of failure, too.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Probably just one flavor, actually: dirtypaint is a busted suite, and the other talos red that I found was a "timeout exceeded," which is the same thing in a different color.
Just unchecked enabled in slavealloc, and added the note pointing to this bug. Pending aki/someone getting a chance to look.
I ran chkdsk on this box and it claims to have fixed some errors. Enabling it one last time before sending to IT.
Depends on: 776656
It's toast. Handed to IT in bug 776656.
Whiteboard: [buildduty] → [buildduty][buildslave][capacity]
Set the hostname and put the slave is back in the pool.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 778774
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Windows claimed the hardware had changed in the last 3 days and it required re-activation. That was successful, and the recent job history is good, so I've left it in production.
Last job was a couple of weeks ago.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Rebooted via ssh. Couldn't VNC but it was probably the issue where buildbot stops but the machine doesn't reboot properly (certainly there were no python processes running).
This has been disabled due to low load in slavealloc; adding [decommission?] to whiteboard.
Whiteboard: [buildduty][buildslave][capacity] → [buildduty][buildslave][capacity][decommission?]
I'm closing this because this bug isn't actionable - the slave is off for the forseeable future.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.