Per comments in bug 947428, I'd like to poke around in one of our test slaves to try and get the soft keyboard running for testing purposes. I'm remote, so I'll need releng vpn access privs / info to connect.
Also, I'll be changing machine config, so I'll need admin privs on the slave.
Details sent in e-mail, please let me know if you have any issues, and unassign yourself from this bug when you're finished with it.
Assignee: nobody → jmathies
Are there any tricks to getting a slave like this running a try build? If I open up a console and get to the right working directory I can run: python -u scripts/scripts/desktop_unittest.py --cfg unittests/win_unittest.py --mochitest-suite mochitest-metro-chrome --blob-upload-branch try --download-symbols ondemand but this runs the latest inbound build. I'd like to run a custom test I've added to mochitests and pushed to try. I can't build locally since there are no build tools installed.
I think I have this working by editing the urls in buildprops.json file.
You guys can take this back, I wasn't able to get this working on our test slaves unfortunately.
(In reply to Jim Mathies [:jimm] from comment #5) > You guys can take this back, I wasn't able to get this working on our test > slaves unfortunately. Thanks Jim, sorry it didn't turn out better!
Status: NEW → RESOLVED
Last Resolved: 5 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.