i#5365 Update ci-aarch64-native workflow with new runner #6549
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding a new self-hosted-runner for this pipeline to enhance the test coverage.
|
This replaces pull request #6293 originally written by @spcaipers-arm |
…kflow-add-sve-runner Change-Id: I9da58958623bf4adf09489fef71a43a8328effb3
Change-Id: Id65891326a40b1e1553e6d2469d816c6867a49e8
Change-Id: I36f410e72cb0c3ac93cf6b3dff8e4199b85d688a
Change-Id: I27de7bcbe581342bf74be1755d7fde9227987c4f
Change-Id: If322146c81ef331081f55659934b8d2a87488ed4
Change-Id: I198e333a5ae13628f81d01ffa7fe95cf15631aff
Change-Id: Ic3fcfb1ac3c43e3ec2608a7b8e198bb1ebe218e6
Change-Id: I69b84e7df93bb2314de116be01e7a906632c1785
…h64-workflow-add-sve-runner Change-Id: I8949b79c1c1c48674221475aec7096bc38eb0dda
Change-Id: I0d8f9d37ec0e5222ddcee5d9e2d4c7c5bffb73c0
AssadHashmi
approved these changes
Feb 12, 2024
|
|
xdje42
added a commit
that referenced
this pull request
Mar 8, 2024
There are currently two workflows name "ci-aarchxx" which is confusing. The ci-aarch64-native workflow was renamed to ci-aarchxx in #6549 with the goal of being consistent with other architecture workflows. However, this introduced the ambiguous "ci-aarchxx" naming. Fix this by renaming ci-aarchxx.yml -> ci-aarchxx-cross.yml, and renaming ci-aarch64-native.yml -> ci-aarchxx.yml. Furthermore, rename the aarchxx "cross" workflow to ci-aarchxx-cross. This accomplishes three things: 1) Naming is consistent with the other workflow files: native workflows are named "ci-$ARCH" and live in file "ci-$ARCH.yml". 2) All workflows have unique names. 3) The yml file and workflow have the same name. In this part one we rename the cross ci-aarchxx to ci-aarchxx-cross, in the workflow name and yml file name. In part two to follow (#xyz) we will leave the workflow name alone, but still rename the file from ci-aarch64-native.yml to ci-aarchxx.yml. The renaming is split into two to better preserve the history: Git can track file renamings, but not when the original file is also replaced with something different. Issue #6678
xdje42
added a commit
that referenced
this pull request
Mar 8, 2024
… file There are currently two workflows name "ci-aarchxx" which is confusing. The ci-aarch64-native workflow was renamed to ci-aarchxx in #6549 with the goal of being consistent with other architecture workflows. However, this introduced the ambiguous "ci-aarchxx" naming. Fix this by renaming ci-aarchxx.yml -> ci-aarchxx-cross.yml, and renaming ci-aarch64-native.yml -> ci-aarchxx.yml. Furthermore, rename the aarchxx "cross" workflow to ci-aarchxx-cross. This accomplishes three things: 1) Naming is consistent with the other workflow files: native workflows are named "ci-$ARCH" and live in file "ci-$ARCH.yml". 2) All workflows have unique names. 3) The yml file and workflow have the same name. In part one (#xyz) we renamed the cross ci-aarchxx to ci-aarchxx-cross, in the workflow name and yml file name. In this part two we leave the workflow name alone, but still rename the file from ci-aarch64-native.yml to ci-aarchxx.yml. The renaming is split into two to better preserve the history: Git can track file renamings, but not when the original file is also replaced with something different. Fixes #6678
xdje42
added a commit
that referenced
this pull request
Mar 12, 2024
…ss (#6696) There are currently two workflows name "ci-aarchxx" which is confusing. The ci-aarch64-native workflow was renamed to ci-aarchxx in #6549 with the goal of being consistent with other architecture workflows. However, this introduced the ambiguous "ci-aarchxx" naming. Fix this by renaming ci-aarchxx.yml -> ci-aarchxx-cross.yml, and renaming ci-aarch64-native.yml -> ci-aarchxx.yml. Furthermore, rename the aarchxx "cross" workflow to ci-aarchxx-cross. This accomplishes three things: 1. Naming is consistent with the other workflow files: native workflows are named "ci-$ARCH" and live in file "ci-$ARCH.yml". 2. All workflows have unique names. 3. The yml file and workflow have the same name. In this part one we rename the cross ci-aarchxx to ci-aarchxx-cross, in the workflow name and yml file name. In part two to follow (#6697) we will leave the workflow name alone, but still rename the file from ci-aarch64-native.yml to ci-aarchxx.yml. The renaming is split into two to better preserve the history: Git can track file renamings, but not when the original file is also replaced with something different. Issue #6678 Co-authored-by: Joshua Warburton <[email protected]>
xdje42
added a commit
that referenced
this pull request
Mar 13, 2024
… file There are currently two workflows name "ci-aarchxx" which is confusing. The ci-aarch64-native workflow was renamed to ci-aarchxx in #6549 with the goal of being consistent with other architecture workflows. However, this introduced the ambiguous "ci-aarchxx" naming. Fix this by renaming ci-aarchxx.yml -> ci-aarchxx-cross.yml, and renaming ci-aarch64-native.yml -> ci-aarchxx.yml. Furthermore, rename the aarchxx "cross" workflow to ci-aarchxx-cross. This accomplishes three things: 1) Naming is consistent with the other workflow files: native workflows are named "ci-$ARCH" and live in file "ci-$ARCH.yml". 2) All workflows have unique names. 3) The yml file and workflow have the same name. In part one (#6696) we renamed the cross ci-aarchxx to ci-aarchxx-cross, in the workflow name and yml file name. In this part two we leave the workflow name alone, but still rename the file from ci-aarch64-native.yml to ci-aarchxx.yml. The renaming is split into two to better preserve the history: Git can track file renamings, but not when the original file is also replaced with something different. Fixes #6678
xdje42
added a commit
that referenced
this pull request
Mar 13, 2024
#6705) There are currently two workflows name "ci-aarchxx" which is confusing. The ci-aarch64-native workflow was renamed to ci-aarchxx in #6549 with the goal of being consistent with other architecture workflows. However, this introduced the ambiguous "ci-aarchxx" naming. Fix this by renaming ci-aarchxx.yml -> ci-aarchxx-cross.yml, and renaming ci-aarch64-native.yml -> ci-aarchxx.yml. Furthermore, rename the aarchxx "cross" workflow to ci-aarchxx-cross. This accomplishes three things: 1) Naming is consistent with the other workflow files: native workflows are named "ci-$ARCH" and live in file "ci-$ARCH.yml". 2) All workflows have unique names. 3) The yml file and workflow have the same name. In part one (#6696) we renamed the cross ci-aarchxx to ci-aarchxx-cross, in the workflow name and yml file name. In this part two we leave the workflow name alone, but still rename the file from ci-aarch64-native.yml to ci-aarchxx.yml. The renaming is split into two to better preserve the history: Git can track file renamings, but not when the original file is also replaced with something different. Fixes #6678
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update ci-aarch64xx workflow with new runner on SVE hardware.
Adding a new self-hosted-runner for this pipeline to enhance the test
coverage. A list of unit tests which fail intermittently are added to
the ignore list ignore_failures_sve in runsuite_wrapper.pl.
Issue: 5365