Sorry about this, but I've thought of things to try on a test machine in parallel with the profiling activity, so ideally I would have both a emulator build instance and an emulator test instance.
Email sent to dminor for further instructions. Loaning slaves: - tst-linux64-ec2-dminor.test.releng.use1.mozilla.com Hi dminor, I am going to assign this to you to keep track of the loan(s). When you are finished with the loan(s) forever, please comment 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. Comment again when you want it started back up. * For really fast turnaround, ping #releng (look for nick with 'buildduty')
You can go ahead and try to connect.
(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #2) > You can go ahead and try to connect. Working great, already running tests, thanks!
I would like to rule out AWS instance type as having a substantial impact on runtimes. Would it be possible to relaunch this as a c3.large? I would only require it for around 2 hours.
re-launched as c3.large (stop, change instance type, start)
All done, thanks!
reclaimed. slave and DNS records have been destroyed.