Closed
Bug 985741
Opened 11 years ago
Closed 11 years ago
Loan an ami-3ac4aa0a instance to Tim Abraldes
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: TimAbraldes, Assigned: TimAbraldes)
References
Details
+++ This bug was initially created as a clone of Bug #974634 +++
I've heard that I need to request an Amazon instance to help green up our Win64 tests. This is that request
Updated•11 years ago
|
Summary: Loan an ami-6a395a5a instance to Tim Abraldes → Loan an ami-3ac4aa0a instance to Tim Abraldes
Comment 1•11 years ago
|
||
Details provided via email. Tim: please close this bug when you are finished with the loaner so we can reclaim it. Thanks!
Assignee: jhopkins → tabraldes
Comment 2•11 years ago
|
||
hi there,
friendly poke: this machine has been up for a ~2 weeks. I can't ssh in as I the host to check on latest activity. I'm not exactly sure why. maybe the ssh daemon is not running
At any rate, as an option, we could stop it in between use. Starting and stopping can happen in a flash now that it is all set up. You could request to start it up again here or, for fast turnaround, poke someone in #releng. If you need this continuously running, please ignore this; I do not wish to block.
Assignee | ||
Comment 3•11 years ago
|
||
Actually I'm not currently using the loaner since I've been asked to look at process sandboxing instead of these win64 test failures. Feel free to reclaim the loaner!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
sounds good.
this instance has been terminated. A/PTR records destroyed. vpn access revoked.
Updated•7 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
•