Closed Bug 715219 Opened 10 years ago Closed 10 years ago

tegra recovery

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bear, Unassigned)

Details

(Whiteboard: [buildduty][tegra])

Attachments

(1 file)

tegra-230 and tegra-268 are refusing to play nice with the others.

multiple PDU hits and they still are offline
colo-trip: --- → mtv1
Whiteboard: [buildduty][tegra]
Assignee: server-ops-releng → jwatkins
tegra-268 come up after a pdu cycle
tegra-230 has unpredictable results during boot up.  sometimes it boots, sometimes it doesn't. So I have replaced tegra-230 with tegra-287
Assignee: jwatkins → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
Priority: -- → P3
this should have been done by me - I'll knock it out in the morning
Assignee: nobody → bear
tegras.json change and foopy19 updating done

committed changeset 2119:68d9f03adb0f
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Please add the tegra to the *config.py so tegra-287 stops trying to connect without the buildmaster knowing about it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Attachment #589575 - Flags: review?(aki) → review+
Comment on attachment 589575 [details] [diff] [review]
off by one fix for tegra range in *_config.py

committed changeset 5311:a14143c88f24
Attachment #589575 - Flags: checked-in+
tegra-268 still won't stay up, do we need a new bug for it at this point?
tegra 268 needs to be marked for recovery - placing into the buildduty queue
Assignee: bear → nobody
Priority: P3 → --
closing - tegra-268 is up and running
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.