Skip to content

request: access to the AIX CI Machine #3571

Closed

Description

@abmusse

I would like to gain access to the AIX CI Machine to debug a test failure in libuv

Ref: libuv/libuv#4222 (comment)

Activity

  1. richardlau commented on Nov 15, 2023

    @richardlau
    Member

    +1

  2. richardlau commented on Nov 16, 2023

    @richardlau
    Member

    Since @abmusse isn't a collaborator this request falls under https://github.com/nodejs/build/blob/main/GOVERNANCE.md#temporary-access

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

    Yes. @abmusse is attempting to unblock updating libuv in Node.js nodejs/node#50650.

    • Is the individual a collaborator. If so then access should be allowed provided the first point is satisfied.

    No.

    • Length and consistency of involvement with Node.js working groups and/or community.

    He's been working on Node.js since February (nodejs/node#46546).
    Pull requests in nodejs/node.
    Pull requests in libuv/libuv.

    • Consequences to the individual in case of misbehaviour. For example, would they potentially lose their job if they were reported as mis-behaving to their employer ? Would being banned from involvement in the Node.js community negatively affect them personally in some other way ?

    Yes, he works for IBM.

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

    I'll vouch for him. He's working with @mhdawson and myself on supporting IBM platforms in Node.js.

  3. mhdawson commented on Nov 17, 2023

    @mhdawson
    Member

    +1 from me

  4. richardlau commented on Dec 18, 2023

    @richardlau
    Member

    Checked with @abmusse and he would still like access. Since no objections I'll proceed with granting access to one of our AIX machines.

  5. richardlau commented on Dec 18, 2023

    @richardlau
    Member

    I've marked test-ibm-aix72-ppc64_be-2 offline in Jenkins and have added @abmusse 's ssh keys to it. Further details have been sent to @abmusse.

  6. richardlau commented on Oct 9, 2024

    @richardlau
    Member

    @abmusse is now a member of the working group so automatically has access. We don't need a separate issue to track anymore.

  7. targos commented on Dec 22, 2024

    @targos
    Member

    I removed @abmusse's keys and put the machine back online.

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions