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.

Sign up for GitHub

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

Jump to bottom

FYI access to test-ibm-rhel8-x64-1 given to @mcollina #2897

Closed
richardlau opened this issue Mar 15, 2022 · 5 comments
Closed

FYI access to test-ibm-rhel8-x64-1 given to @mcollina #2897

richardlau opened this issue Mar 15, 2022 · 5 comments
Labels
access request

Comments

@richardlau
Copy link
Member

Refs: pinojs/pino#1368

FYI as per https://github.com/nodejs/build/blob/master/GOVERNANCE.md#temporary-access I've taken test-ibm-rhel8-x64-3 offline from the test CI and put @mcollina 's ssh keys on it so he can look at a CITGM failure.
@mcollina
Copy link
Member

What's the ip and username I can use for logging in?

@mcollina
Copy link
Member

I've found the instructions on the other thread!

@richardlau richardlau changed the title FYI access to test-ibm-rhel8-x64-3 given to @mcollina FYI access to test-ibm-rhel8-x64-1 given to @mcollina Mar 23, 2022
@richardlau
Copy link
Member Author

Removed Matteo's key from test-ibm-rhel8-x64-1 and returned it to the CI. I've taken test-ibm-rhel8-x64-1 offline from Jenkins and added Matteo's keys to that one.

Refs: pinojs/pino#1375

@mcollina
Copy link
Member

mcollina commented Apr 9, 2022

After 17 days and many attempts, this is fixed. Thanks to all!

@richardlau
Copy link
Member Author

Thank you @mcollina! I've removed your keys from the machine and returned it to the CI pool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
access request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mcollina @richardlau