Closed Bug 805259 (bld-lion-r5-043) Opened 12 years ago Closed 7 years ago

bld-lion-r5-043 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mozilla, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1920] [buildduty][buildslaves][capacity])

No description provided.
Depends on: 805262
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
This is showing failures on multiple branches in the same jit-test. Please disable.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 882515
disabled in slavealloc
Back in preproduction.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Blocks: 905742
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer blocks: 905742
Depends on: 905742
No longer depends on: 805177, 805262, 882515
QA Contact: armenzg → bugspam.Callek
slavealloc says its attached to massimo's master...
Assignee: nobody → mgervasini
Massimo, are you still using this? (if not can you unassign from yourself)
Assignee: mgervasini → nobody
Flags: needinfo?(mgervasini)
Hi Callek, I'm done with it. Forwarding your needinfo request to Jordan (slavealloc says he is using it)
Flags: needinfo?(mgervasini) → needinfo?(jlund)
still using it. I'll re-image and return it to the pool once I'm done.
Assignee: nobody → jlund
Flags: needinfo?(jlund)
back in dev pool
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Depends on: 1087013
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [buildduty][buildslaves][capacity] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1920] [buildduty][buildslaves][capacity]
Morgan seems to be using this slave now. Re-assigning. Morgan: just un-assign the bug when you're done and it will magically reappear in the buildduty queue.
Assignee: jlund → winter2718
Handing this off to Ben since he needed the slave.
Assignee: winter2718 → bhearsum
I actually didn't end up using it...
Assignee: bhearsum → nobody
Testing desktop repacks
Assignee: nobody → mgervasini
Assignee: gervaland → nobody
Are you using this machine? In slavealloc it's locked to your dev-master.
Flags: needinfo?(mshal)
I had been using it off and on to test S3 changes. I'm not at the moment though, and likely won't be for the next few weeks so I've unlocked it. Will we still have a preprod OSX machine available? Or is it going into production?
Flags: needinfo?(mshal)
If you don't need it for a few weeks, I can reimage it and allocate it to production builds unless you need the current state when you resume testing in a few weeks. Please let me know what you would prefer.
Flags: needinfo?(mshal)
Nope, I don't need the current state. I've just found it handy to have one ready for staging when things come up. Feel free to reimage and we can always reallocate one when needed!
Flags: needinfo?(mshal)
Returned to production
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Re-imaged and enabled in slavealloc
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Did a reimage and enabled it back.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 7 years ago
Resolution: --- → FIXED
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.