Closed Bug 889962 Opened 11 years ago Closed 10 years ago

Loan talos-linux64-ix-001 to dminor, ctalbert & gbrown

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: gbrown)

References

Details

(Whiteboard: [buildduty])

as part of figuring out how to setup android-x86 testing on emulator-on-ix-hardware, ctalbert needs an ubuntu64 ix node to experiment on and evaluate setup instructions. With any luck those instructions can be turned into puppet scripts. (From previous experiments, running emulators-on-aws does not seem to work, hence the hardware.)
Also, gbrown and dminor will probably also need access to this box so that they can see the machine and help get things stood up quickly.
Whiteboard: [buildduty]
Does this have to be hardware? AFAIK, we run the same tests on hardware and aws ubuntu machines.
Yes, it has to be hardware.
The x86 emulators do not work in AWS. We could never get them to boot there due to the way the x86 emulators re-use the underlying hardware.
Depends on: 890047
Argh, got midaired last night! I set aside talos-linux64-ix-001.test.releng.scl3.mozilla.com for this. Clint, I believe I gave you the password over IRC last night?
(In reply to Ben Hearsum [:bhearsum] from comment #5) > Clint, I believe I gave you the password over IRC last night? Yes you did, and I have verified that I can access it - thanks!
clint, please reassign to nobody@ when you're done with this.
Assignee: nobody → ctalbert
Component: Release Engineering: Machine Management → Release Engineering: Loan Requests
Product: mozilla.org → Release Engineering
Did someone change the password on this loaner? I cannot ssh into it now; after entering the password, I get "Permission denied, please try again.". It was fine this morning.
I added gbrown's pub key to the authorized_keys.
Blocks: 891959
I believe we're done (or close to done) with this host. When ready to return simply close the bug, we will re-image it and put it back into the pool.
Assignee: ctalbert → gbrown
Status: NEW → ASSIGNED
Summary: loan ubuntu64 ix node to ctalbert → Loan talos-linux64-ix-001 to dminor, ctalbert & gbrown
I will likely keep using it for another week or two -- it has been super-useful!
gbrown, dan, are you still using this?
Flags: needinfo?(gbrown)
Flags: needinfo?(dminor)
I am not.
Flags: needinfo?(dminor)
I am still using it. Always hoping to wrap this work up and move on soon....
Flags: needinfo?(gbrown)
This loan has been very useful and I am still finding uses for it. But it suddenly started giving me trouble, starting between Jan 13 23:32 and Jan 14 00:30. I can no longer run the emulator; it complains SDL init failure, reason is: No available video device stackoverflow articles suggested I check my DISPLAY env var. I use DISPLAY=:0.0, and that hasn't changed for months. I tried rebooting -- no change. :Callek kindly investigated today but could not find the cause. Ben -- Could you have a look as well? If necessary, I don't mind if we re-image (I have everything I need backed up now).
Flags: needinfo?(bhearsum)
It seems to work fine for me. I logged in as cltbld, ran /home/cltbld/gbrown/runset1, and found this in ps: root 4664 0.0 0.0 58848 3372 ? Ss 06:00 0:00 \_ sshd: root@pts/0 root 4666 0.0 0.0 23828 5020 pts/0 Ss 06:00 0:00 | \_ -bash cltbld 4787 0.0 0.0 57712 1628 pts/0 S 06:02 0:00 | \_ su - cltbld cltbld 4865 0.1 0.0 23876 5172 pts/0 S 06:02 0:00 | \_ -su cltbld 5382 0.0 0.0 12304 1188 pts/0 S+ 06:02 0:00 | \_ /bin/bash ./runset1 cltbld 5383 0.4 0.2 59872 16968 pts/0 S+ 06:02 0:00 | \_ python /home/cltbld/gb-mozharness/mozharness/scripts/android_emulator_unittest.py --cfg android/androidx86.py --test-suite mochitest-1 --test-suite jsreftest --download-symbols ondemand cltbld 5519 20.8 7.2 3876488 595236 pts/0 Sl+ 06:03 0:27 | \_ /tools/android-sdk18/tools/emulator64-x86 -avd test-1 -debug init,console,gles,memcheck,adbserver,adbclient,adb,avd_config,socket -port 5554 -qemu -m 1024 -enable-kvm cltbld 5572 22.7 7.0 3192296 577700 pts/0 Rl+ 06:03 0:27 | \_ /tools/android-sdk18/tools/emulator64-x86 -avd test-2 -debug init,console,gles,memcheck,adbserver,adbclient,adb,avd_config,socket -port 5556 -qemu -m 1024 -enable-kvm I double checked by logging in with vnc (need to run 'x11vnc' first) and saw the emulator running. Can you try again?
Flags: needinfo?(bhearsum) → needinfo?(gbrown)
Confirmed -- it is working normally again. I wonder what happened? Thanks!
Flags: needinfo?(gbrown)
(In reply to Geoff Brown [:gbrown] from comment #15) > This loan has been very useful and I am still finding uses for it. > > But it suddenly started giving me trouble, starting between Jan 13 23:32 and > Jan 14 00:30. I can no longer run the emulator; it complains > SDL init failure, reason is: No available video device This happened again. I noticed that there was no X server running. Simply running X from an ssh session allowed the emulator to start.
Just checking in - is this loaner still needed?
Flags: needinfo?(gbrown)
Yes, I'm afraid I keep finding new uses for it! Hope that's okay...
Flags: needinfo?(gbrown)
:gbrown, do you still need this machine?
Flags: needinfo?(gbrown)
No, I do not need it any more. All done - thanks.
Flags: needinfo?(gbrown)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: Loan Requests → Buildduty
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.