-
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 win11 compiled by VS2022 #3901
Comments
+1 from me |
+1 from me. |
@jakecastelli can you give me your and/or @jazelly's email so I can send you login parameters once I prepare a machine for this? (I see Jason's email from his GH profile). |
Thanks @StefanStojanovic! My email address is |
Hi @StefanStojanovic, is there any update about the machine? cheers |
Hey @jakecastelli, I've created the machine. I just need to run a setup on it, and then I'll send you the credentials. |
@jakecastelli I've sent the credentials in an email. |
Credential received! Thank you heaps! |
Hi @StefanStojanovic we have finished using the windows machine to debug and Jason had successfully found and resolved the issue. 🙏 Please feel free to delete the VM when you have time, thanks again everyone! |
Great! I'm glad it was helpful. The machine is deleted now. |
Jason @jazelly and myself are working on this PR nodejs/node#54653, the test works on Mac and Linux but not windows. Jason has a windows PC and it passed locally but consistently fail on CI due to memory access violation.
Would be great to have access to the "win11 compiled by VS2022" machine to debug.
The text was updated successfully, but these errors were encountered: