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

Correct ARMv8 to aarch64 in Jenkins #1837

Open
2 tasks
Willsparker opened this issue Jan 14, 2021 · 10 comments
Open
2 tasks

Correct ARMv8 to aarch64 in Jenkins #1837

Willsparker opened this issue Jan 14, 2021 · 10 comments
Labels

Comments

@Willsparker
Copy link
Contributor

Found as a part of #1716 (comment)

As suggested by @sxa (#1806 (review)), we should change the Jenkins name of the following machines, so they match the inventory.yml, i.e. remove the l from armv(7|8)l:

  • build-packet-ubuntu1804-armv8l-1
  • docker-scaleway-ubuntu1604-armv7l-1

Should just be a case of changing their names, and restarting the Jenkins agent.

@Willsparker Willsparker added this to the January 2021 milestone Jan 14, 2021
@Willsparker Willsparker self-assigned this Jan 14, 2021
@Willsparker Willsparker removed their assignment Jan 14, 2021
@Willsparker
Copy link
Contributor Author

Clearing assignment as I don't have access to the machines to restart the Jenkins agent

@sxa
Copy link
Member

sxa commented Jan 14, 2021

I'm tempted to switch them all over to aarch64 instead of armv8 since I think that name is clearer to most people, and it's consistent with uname and what we use on the download site ... And the build job names

@Willsparker
Copy link
Contributor Author

Yeah, that seems fair - should I rename the issue ? Should ARMv7 remain ARMv7? (I noticed that the job just refers to it as arm)

@Willsparker
Copy link
Contributor Author

@sxa I'm happy to pick this up, as it's blocking me on #1716 , but presumably I'm going to need access to all of the arm64 nodes, so I'm able to restart the Jenkins Agents.

(The following is a list of machines that I don't have access to. I do have it for the rest of the ARMv8 nodes in the inventory)

Node in Inventory IP Other Info
build-linaro-centos76-armv8-2 213.146.141.123
build-packet-ubuntu1804-armv8-1 139.178.82.234
docker-packet-ubuntu1604-armv8-1 147.75.77.146
docker-scaleway-ubuntu1604-armv7-1 51.158.73.136
test-macstadium-macos11-arm64-1 199.7.163.51 (Blocked by #1855 )

@Willsparker Willsparker changed the title Correct armv(7|8)l Jenkins node names Correct ARMv8 to aarch64 in Jenkins Feb 5, 2021
@sxa sxa added the Nagios Nagios monitoring issues label Feb 19, 2021
@Haroon-Khel Haroon-Khel modified the milestones: February 2021, March 2021 Mar 2, 2021
@Haroon-Khel
Copy link
Contributor

@Willsparker Any update on this?

@Haroon-Khel Haroon-Khel modified the milestones: March 2021, April 2021 Apr 6, 2021
@Willsparker
Copy link
Contributor Author

Still waiting on @sxa so I can get access to the above nodes

@Haroon-Khel Haroon-Khel modified the milestones: April 2021, May 2021 May 18, 2021
@sxa sxa self-assigned this May 22, 2021
@sxa
Copy link
Member

sxa commented May 22, 2021

Quick update on this - the Linaro machines are not currently in production, the scaleway ones are going to get decomissioned (and are armv7 not armv8), the packet aarch64 ones listed above are also to be decomissioned soon. We'll need to consider what to do with the macos ones ...

@Haroon-Khel Haroon-Khel modified the milestones: May 2021, June 2021 Jun 21, 2021
@sxa
Copy link
Member

sxa commented Jul 5, 2021

Still considering keeping armv8 since aarch64 will become ambiguous across armv8, armv8.2 (Required by Dragonwell) and the upcoming armv9

@sxa sxa added this to the July 2021 milestone Jul 5, 2021
@Haroon-Khel Haroon-Khel modified the milestones: July 2021, August Aug 4, 2021
@sxa sxa modified the milestones: October 2021, December 2021 Dec 1, 2021
@sxa sxa modified the milestones: December 2021, 2022-01 (January) Jan 6, 2022
@sxa
Copy link
Member

sxa commented Mar 3, 2022

After some discussions with someone at ARM I've come to the conclusion that standardising on aarch64 is the right approach for the naming, so yes we should go for that :-)

@sxa sxa modified the milestones: 2022-04 (April), 2022-06 (June) May 24, 2022
@sxa sxa modified the milestones: 2022-06 (June), 2022-07 (July) Jun 30, 2022
@sxa sxa modified the milestones: 2022-07 (July), 2022-10 (October) Sep 1, 2022
@sxa sxa modified the milestones: 2022-10 (October), Backlog Dec 1, 2022
@sxa
Copy link
Member

sxa commented Nov 20, 2024

The new ones added in #2478 #3586 have all been added as armv8 or armv8l e.g.

We should bump up the priority of this for usability/simplicity reasons - adding to Q4 plan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

3 participants