Closed
Bug 1150289
Opened 9 years ago
Closed 9 years ago
Slave loan request for a try-linux64-spot vm to try reproducing a cgc test failure
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
I have a cgc test failure that seems to reproduce on try but not locally for me or anyone else who's tried to reproduce it. I'd like to see if I can reproduce by running directly on the machine it's running on. You can see the sort of slave involved at <https://treeherder.mozilla.org/#/jobs?repo=try&revision=375a3cf6aabe>: try-linux64-spot-068, try-linux64-spot-062, try-linux64-spot-142, etc.
Comment 1•9 years ago
|
||
Email sent to Boris for further instructions. Loaning slaves: - dev-linux64-ec2-bzbarsky Hi Boris, I am going to assign this to you to keep track of the loan. When you are finished with the loan forever, please comment stating so here in the bug, and mark the bug as RESOLVED. By the way, now that this aws instance has been created, starting and stopping it can happen in a flash! If you are not going to be using this machine for multiple hours, let us know in this bug and we can stop it. Comment again when you want it started back up. * For faster turnaround, ping #releng (look for nick with 'buildduty')
Assignee: nobody → bzbarsky
Updated•9 years ago
|
Blocks: dev-linux64-ec2-bzbarsky
![]() |
Assignee | |
Comment 2•9 years ago
|
||
I'm done with this slave, thank you.
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•