1404223 - Slave loan request for a t-w1064-ix machine

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

To investigate bug 1397201 I would like to have a Windows loaner of type t-w1064-ix. Thanks

Comment 1

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Email sent to whimboo for further instructions. 

Loaning machines: 
    -  t-w1064-ix-060

Hi Henrik, 

I am going to assign this to you to keep track of the loan. 

When you are finished with the loan forever, please comment stating so here in the bug, and mark the bug as RESOLVED.

Comment again when you want it started back up.
* For faster turnaround, ping #releng (look for nick with 'buildduty')

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Sorry but I was sidetracked last week, and I will be mostly out the next week. I don't want to see this machine lingering around anytime longer. So please put it back into the pool.

Comment 3

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Credentials were removed from Inventory and machine was returned to production.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andrei, I have to reopen this bug given that those failures increased a lot over the last days and I'm not able to reproduce this situation on any other Windows 10 machine/VM I have around locally. Also setting up a TC loaner seem to be more complicated, so that I would have to do all the GPG stuff first which I don't have the time for. Thanks.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Putting ni? on Andrei to prepare one of the machines for me.

Comment 6

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Henrik I loaned for you exactly the same machine with the same credentials as before,I also re-sent the sent mail that was before with all info.

When you are finished with the loan forever, please comment stating so here in the bug, and mark the bug as RESOLVED.

Comment again when you want it started back up.
* For faster turnaround, ping #releng (look for nick with 'buildduty')

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Hm, I can access the Win10 machine, and use the mouse to control everything. But the keyboard only works in the mozilla-build shell. Any other place (start menue, Edge browser) allows me to type. This blocks me from getting all the builds I need. I tested via screensharing and RealVNC on MacOS 10.12.

Comment 8

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

(In reply to Henrik Skupin (:whimboo) from comment #7)
> Hm, I can access the Win10 machine, and use the mouse to control everything.
> But the keyboard only works in the mozilla-build shell. Any other place
> (start menue, Edge browser) allows me to type. This blocks me from getting
> all the builds I need. I tested via screensharing and RealVNC on MacOS 10.12.


Unfortunately this is the general configuration for windows10, in the past there was the possibility to connect using RDP(where maybe you could have more options for keyboard) but the configuration from OU for loaner does not support this so you can only connect with VNC.
The OU settings is not managed by us,is managed by RelOPs team so we can't help with the keyboard issue.

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andrei, you mean that it is expected that I cannot use the keyboard for most of the applications but only for a command interpreter as I can start with Mozilla Build? This is totally annoying. Do you know anyone from RelOps we could talk to here?

Comment 10

[Joel Maher ( :jmaher ) (UTC -8)]

if this is a hardware machine Q is an expert, I have ni? him for data on comment 9.

the failures look to be on VMs though (we only run reftest/media/clipboard) on hardware, while there is a loaner process there, :rwood found that it was not useful and had to get :grenade to help him setup a loaner that didn't disappear all the time.

Comment 11

[Andrei Obreja [:aobreja NOT AVAILABLE][:buildduty]]

Q,Jake or Dave can help with more information.

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I further have to use this loaner for bug 1391545.

Btw. the keyboard input seems to work sometimes. If it stops I have to restart VNC, and then it works again. It's at least a workaround, and maybe something is broken with this RealVNC software.

Comment 13

[Q]

Try Ultra client  VNC if you can. I can also enable RDP but any graphics and clipboard tests run in that state will most likely have issues.

Comment 14

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Q from comment #13)
> Try Ultra client  VNC if you can. I can also enable RDP but any graphics and
> clipboard tests run in that state will most likely have issues.

Unfortunately this isn't available for MacOS users. So I can only use screensharing or RealVNC. But as said earlier, I got it working now.

Comment 15

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We solved the problem, so I no longer need this loaner. Thanks.