Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

temporary test server access for @thefourtheye #583

Closed
jbergstroem opened this issue Jan 4, 2017 · 15 comments
Closed

temporary test server access for @thefourtheye #583

jbergstroem opened this issue Jan 4, 2017 · 15 comments

Comments

@jbergstroem
Copy link
Member

In order to resolve issues for a set of hosts with stalling tests related to nodejs/node#10456, @thefourtheye is requesting access to a few machines.

@thefourtheye could you perhaps list the one's you want to do further investigation with so we can approve and arrange it?

@thefourtheye
Copy link

Whenever I run CI on that PR, the leftover processes will be there in almost all the machines. So I'll have to clean them in all of them. I am fixing them case by case basis, e.g nodejs/node#10597 fixes SmartOS failures (hopefully).

Is it possible to get permissions for all of them?

@jbergstroem
Copy link
Member Author

Since Linux looks mostly ok, how about we for instance start with smartos, plinux and windows? I can facilitate the former; not sure how we create temporary accounts for windows. @joaocgreis?

@Trott
Copy link
Member

Trott commented Jan 4, 2017

The only ones that I noticed stalled jobs on were SmartOS and FreeBSD, so I'd be sure to include access to those two at a minimum.

@jbergstroem
Copy link
Member Author

jbergstroem commented Jan 4, 2017

@Trott: @thefourtheye mentioned [on IRC] that he was running FreeBSD locally and that the failures/stalls was similar across os'es. I think he's doing local testing at the moment.

@thefourtheye
Copy link

Setting up the FreeBSD vm in a slow internet connection. I'll update the status about that tomorrow.

@mhdawson
Copy link
Member

mhdawson commented Jan 4, 2017

Let me or @gibfahn know when you need access to plinux/aix

@jbergstroem
Copy link
Member Author

I can arrange it as well; seems like we have me and @mhdawson (so far?) approving your access.

@gibfahn
Copy link
Member

gibfahn commented Jan 4, 2017

+1 to giving @thefourtheye access

@joaocgreis
Copy link
Member

I also approve giving @thefourtheye access. According to our docs, giving temporary access to a collaborator can be done immediately, so I went ahead and created a temporary account on a Windows machine (emailed credentials). Given that stalling tests can interfere with normal CI runs, I disconnected the machine from CI.

@jbergstroem
Copy link
Member Author

@joaocgreis true. I will help facilitate the rest on demand, as well as making a note here on when access is granted and finally revoked.

@mhdawson
Copy link
Member

mhdawson commented Jan 5, 2017

To confirm +1 from me.

@thefourtheye
Copy link

Thanks people :-) I finally managed to setup a FreeBSD instance locally and test this. nodejs/node#10822 looks like fixes it. PTAL.

@joaocgreis
Copy link
Member

@thefourtheye Still using the machine? If you are, no rush, just let me know when you're done!

@gibfahn
Copy link
Member

gibfahn commented Oct 22, 2017

ping @thefourtheye @joaocgreis , I think this can be revoked now.

@thefourtheye
Copy link

@gibfahn @joaocgreis Yes, this can be revoked now. Thanks :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants