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.

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

Access request for <rtoyonag> #3381

Closed
1 of 4 tasks
roberttoyonaga opened this issue Feb 12, 2024 · 10 comments
Closed
1 of 4 tasks

Access request for <rtoyonag> #3381

roberttoyonaga opened this issue Feb 12, 2024 · 10 comments
Assignees

Comments

@roberttoyonaga
Copy link

roberttoyonaga commented Feb 12, 2024

NOTE: THIS ISSUE SHOULD NOT BE CLOSED BY THE ORIGINATOR IF ACCESS IS GRANTED.
When the access is no longer needed please add a comment and a member
of the infrastructure team will revoke it and close the issue.

Required access level (Delete as appropriate). Note that you should only
request the minimum level that is required to solve your problem

  • Non-privileged
  • jenkins user
  • root/Administrative
  • other (Please specify):

System for which access is needed:
https://ci.adoptium.net/computer/test-azure-win2016-x64-1/

Please explain why you need this access including whether it is a temporary or permanent request:
Temporary request to investigate jdk17 windows 32 bit issues with JFR tests adoptium/aqa-tests#4352 (comment)
https://ci.adoptium.net/view/Test_grinder/job/Grinder/8771/testReport/

@sxa
Copy link
Member

sxa commented Feb 14, 2024

Hi @roberttoyonaga - can you clarify why Administrative level access is required for this? In general our tests run as a normal user without special privileges so I would expect that any debugging of failures would not require administrative access.

@sxa
Copy link
Member

sxa commented Feb 14, 2024

@andrew-m-leonard It looks like we've got three machines assigned for reproducible build work - are they still required?

  • adopt-bld-repro1 at 20.77.116.89
  • adopt-bld-repro2 at 20.68.163.224
  • andrew-repro-test at 20.123.40.15

Are these still required? And if not can they be deleted or given to Robert for now if he requires Administrative access?

@andrew-m-leonard
Copy link
Contributor

@sxa I'd like to keep andrew-repro-test at 20.123.40.15 please, as that's a Windows box I am currently using for repro build testing, is there a place I can see where it is assigned to me?

The other two can be removed
thanks Stewart

@sxa
Copy link
Member

sxa commented Feb 14, 2024

@sxa I'd like to keep andrew-repro-test at 20.123.40.15 please, as that's a Windows box I am currently using for repro build testing, is there a place I can see where it is assigned to me?

The other two can be removed thanks Stewart

Sure no problem - you can't see where it's assigned to you unless it's through an issue such as this - otherwise it's only visible in the Azure admin console by how they were named :-)

@roberttoyonaga
Copy link
Author

Hi @roberttoyonaga - can you clarify why Administrative level access is required for this? In general our tests run as a normal user without special privileges so I would expect that any debugging of failures would not require administrative access.

Hi @sxa this is my first time through this workflow so I am not 100% sure what level of access I'll need to complete this task. I don't know what these machines are already equipped with, but I'll need to build and install the JDK, as well as debugging tools like gdb and a terminal editor. If you don't foresee me needing root access for this then normal user privileges are likely fine for me.

@sxa
Copy link
Member

sxa commented Feb 14, 2024

Hi @roberttoyonaga - can you clarify why Administrative level access is required for this? In general our tests run as a normal user without special privileges so I would expect that any debugging of failures would not require administrative access.

Hi @sxa this is my first time through this workflow so I am not 100% sure what level of access I'll need to complete this task. I don't know what these machines are already equipped with, but I'll need to build and install the JDK, as well as debugging tools like gdb and a terminal editor. If you don't foresee me needing root access for this then normal user privileges are likely fine for me.

Gotcha - thanks. No idea about gdb as I've never tried using that on Windows, but in general all of the other things you need can definitely be done as a normal user :-)

Also our windows machines aren't set up with ssh so you'd be getting access to the machine for rdp.

@roberttoyonaga
Copy link
Author

Gotcha - thanks. No idea about gdb as I've never tried using that on Windows, but in general all of the other things you need can definitely be done as a normal user :-)

In that case, that sounds good to me!

@sxa
Copy link
Member

sxa commented Feb 15, 2024

Access granted to test-azure-win2016-x64-1 - will send details through another forum :-)

@roberttoyonaga
Copy link
Author

Hi @sxa I am finished with the windows machine for now. I'd like to return my access. Thank you!

@sxa
Copy link
Member

sxa commented Mar 5, 2024

Thanks - account has now been removed. Closing

@sxa sxa closed this as completed Mar 5, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in 2024 1Q Adoptium Plan Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants