Bug 1053703 was backed out for unknown reasons. I need a loaner machine of type b2g_ubuntu64_vm in order to diagnose this issue.
Email sent to :rickychien with access instructions. Loaning slaves: * tst-linux64-ec2-rchien Hi Ricky, I am going to assign this bug to you to keep track of the loan. When you are finished with the loan forever, please comment here stating so, and mark this 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. This saves a little money, but every bit helps. Comment again when you want it started back up. For really fast turnaround, ping #releng (look for nick with 'buildduty')
Assignee: nobody → ricky060709
Status: NEW → ASSIGNED
Summary: Requesting a loaner machine b2g_ubuntu64_vm to diagnose bug 1053703 → Requesting a loaner machine bld-linux64 to diagnose bug 1053703
New build instance is ready. All the access information from the previous email remains the same. The new instance is: dev-linux64-ec2-rchien.dev.releng.use1.mozilla.com (10.134.52.76)
Oops! I cannot access to the new machine.
I saw response messages from new machine through SSH but got stuck in entering password.
Hi Cooper, Fortunaltely, bug 1053703 has been resolved. You can take back this loaner machine. Thanks for your help. :)
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: Loan Requests → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.