-
Notifications
You must be signed in to change notification settings - Fork 166
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
Request access to rhel8-x64-release
#3207
Comments
Does it need to be a release machine? We do not normally give temporary access to those. |
No, I don't think it has to be a release machine. I'm okay with getting access to a non-release machine which has the same OS, arch and compiler if possible. |
+1 from me. I'll add you to one of the rhel8-x64 test machines on Monday afternoon/evening if nobody else from build does before then. |
I added your keys to test-ibm-rhel8-x64-3
@richardlau It's the first time I do this. Please tell me if I did something wrong. |
@targos I'm done, thanks! |
Keys removed. Node back online. |
I would need access to this system in order to debug an SEA crash on Linux.
See conversation in nodejs/postject#76 (comment).
cc @targos
The text was updated successfully, but these errors were encountered: