Bug 715605 (talos-r4-lion-036)

talos-r4-lion-036 problem tracking

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
7 years ago
6 months ago

People

(Reporter: bear, Unassigned)

Tracking

Details

(Whiteboard: [buildduty][buildslaves][capacity])

Comment hidden (empty)
(Reporter)

Updated

7 years ago
See Also: → bug 711844
Whiteboard: [buildduty][buildslave]
Assignee: server-ops-releng → jwatkins
This has been re-imaged. Kicking back to releng for post re-image work.
Assignee: jwatkins → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Summary: please reimage talos-r4-lion-036.build.scl1.mozilla.com → talos-r4-lion-036.build.scl1.mozilla.com post re-image work needed
Priority: -- → P3

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED

Comment 2

7 years ago
[14:34]	<philor>	looks like talos-r4-lion-036 got resuscitated yesterday, but it isn't actually well
[14:35]	<philor>	hard though it is to tell with lion, since so many suites are permafail, but https://tbpl.mozilla.org/php/getParsedLog.php?id=8646474&tree=Firefox ain't normal
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
If you want to indulge my wild guesses, running a memory checker on it could possibly prove interesting.

Updated

7 years ago
Summary: talos-r4-lion-036.build.scl1.mozilla.com post re-image work needed → setup talos-r4-lion-036
Assignee: nobody → bhearsum
Alias: talos-r4-lion-036
Summary: setup talos-r4-lion-036 → talos-r4-lion-036 problem tracking
Since this is part of buildduty and I'm probably not going to be that guy when the dep bug is closed, throwing back.
Assignee: bhearsum → nobody
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
This slave is back from repair and has been re-imaged.

Comment 6

7 years ago
TODO: setup machine
Whiteboard: [buildduty][buildslave] → [buildduty][buildslave] setup re-imaged slave
Back in production.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Maybe it just doesn't like January: https://tbpl.mozilla.org/php/getParsedLog.php?id=18520642&tree=Mozilla-Inbound is another suspicious crash in the weeds, characteristic of bad RAM.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [buildduty][buildslave] setup re-imaged slave → [buildduty][buildslaves][capacity][needs diagnostics]
Depends on: 887859
Awaiting a proper bringup procedure for this slave class
Testing with PuppetAgain in bug 891880.
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
fullscreen crash -> hdiutil: attach failed - Device not configured, needs a reboot (and needed to have been closed after the very odd diagnostics, since it was back in production).
Whiteboard: [buildduty][buildslaves][capacity][needs diagnostics] → [buildduty][buildslaves][capacity][needs reboot]
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago5 years ago
Resolution: --- → FIXED
Whiteboard: [buildduty][buildslaves][capacity][needs reboot] → [buildduty][buildslaves][capacity]

Updated

6 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.