Temporary access to win-vs2019 machine for @ljharb

[ljharb]

Specifically, to investigate this failure: https://github.com/login/oauth/authorize?client_id=f1ead3ce228ca872c274&scope=read:org,user:email&state=1-IpTYwwEZRvGUXzoJ29.qMV6bW from nodejs/citgm#894

I'm not a collaborator, but I'm an org owner via moderation, if that level of trust qualifies.

Does the scope and size of the need justify providing access.

The goal is to eliminate this false positive in CIGTM tests for tape, so that release test failures are meaningful. Not sure if that justifies it or not.

Consequences to the individual in case of misbehavior.

I participate extensively in node; and I'm on the OpenJS Foundation Board, and Cross Project Council. Being banned would likely threaten all of those positions as well as my standing in the community.

Are there collaborators who work with the individual and can vouch for them.

Hopefully some collaborators can vouch for me :-)

[Trott]

Anyone trusted and competent to debug issues on our Windows CI machines is 💯 by me. +1

[joaocgreis]

@ljharb I've sent you login details by email. Please let us know when you no longer need it. Thanks!

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

[ljharb]

I've still not resolved the issue, but I haven't heard further reports from citgm either, so maybe the issue's resolved itself? Either way, I'd prefer the issue to stay open for now.

[BethGriggs]

IIRC this was about tape failing on Windows (nodejs/citgm#895). It's still an issue:

• https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3087/nodes=win-vs2019/testReport/(root)/citgm/tape_v5_6_3/ (v18.14.0 run from yesterday)

[ljharb]

Thanks, I'll keep trying to find time to debug it further.

[StefanStojanovic]

Hi @ljharb. Do you still need the machine created for this investigation?

[ljharb]

@StefanStojanovic i've spent a number of hours investigating but haven't had the time to complete it. If leaving the access open is a problem, feel free to remove it, and I can reopen this issue (or file a new one) when i have the time in the future - if it's not a problem then i can just keep trying to get back to it :-)

[StefanStojanovic]

It's not a problem, we'll keep it running, and I'll be checking on it from time to time.

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.