Access to test-digitalocean-freebsd11-x64-2 for @ofrobots

[Trott]

Can we get ssh access to test-digitalocean-freebsd11-x64-2 or similar for @ofrobots to debug nodejs/node#21038?

@nodejs/build

[refack]

+1

[refack]

@ofrobots probably better to look at a linuxONE machine, were we have higher reproducibility. NM
Do you still have the "throw-away" key I made you last time?

[refack]

Anyway I added ****ASVRmA ofrobots@lemonhope & the thorwaway ***S+x93aBw== rsa-key-20180627

[refack]

onn it's freebsd@107.170.28.213

[refack]

so I added the RSA ***HyMChH7st one as well

[ofrobots]

Thanks. I can login.

[ofrobots]

Can I also get access to a LinuxONE machine? The issue is far too flaky on the FreeBSD machine in my experimentation to be able to make conclusive progress.

[refack]

Added to rhel72-s390x-3

[ofrobots]

I no longer need this access.

[refack]

Keys Removed.
@ofrobots Thank you very much for the fix, and for following up on this access request.

[Trott]

Turns out @ofrobots needs access again. Can we just re-add the keys and re-open this? Or should we open a new issue?

[refack]

restored keys to same two computers

[ofrobots]

@refack thanks. I don't seem to be able to get in though:

❯ ssh freebsd@107.170.28.213
Password for freebsd@test-digitalocean-freebsd11-x64-2:

[refack]

@ofrobots, oops didn't hit save.
Should be there now.

[ofrobots]

At present, I no longer need access to the FreeBSD, Linux on zArch, or the windows machine. I can raise a separate issue if the need arises again. In the meanwhile the resources can go back into the pool (if they are being sequestered).

[refack]

Thanks for following up.