[jdk11u-dev] RFR: 8253424: Add support for running pre-submit testing using GitHub Actions [v2]

[openjdk-notifier [bot]]

On Wed, 4 Aug 2021 21:51:15 GMT, Christoph Langer <clanger at openjdk.org> wrote:

>> This is the backport of the GitHub Actions workflow to JDK11 Updates
>> 
>> It is close to the current state of the workflow in head openjdk/jdk, except for the following modifications:
>> 
>> - No Windows Aarch64
>> - No MacOs Aarch64
>> - Used jtreg5.1-b01 vs. jtreg-6+1 (which means a slight modification for the steps that build it). This can/should probably be updated later
>> - Use Adopt OpenJDK 11.0.11 as boot JDK (I don't know whether Adoptium 11.0.12 is ready. I guess this can be changed later on as well)
>> - Computation of JDK_VERSION used in bundle names: It is different because 11u is an update release (e.g. we have to account for 11.0.13 vs. only 11)
>> - Added a step "Fix jtreg permissions" because configure on Linux/Mac would bail out otherwise. I don't know why this is not needed in head. Maybe configure was improved?
>> - Use gcc 9 vs. gcc 10 on Linux. I chose to take what we use in SAP's nightly tests for the moment. We could probably spend some effort later to update the code to be able to compile on gcc 10.
>> - No gtest support
>> - Make target for test runs is "run-test-prebuilt" vs. "test-prebuilt". There was some refactoring between 11 and 18.
>> - MacOS bundle names contain 'osx' (vs 'macos' in head)
>> 
>> To make the pipeline work and results look greenish, I proposed 6 other backports to be done before merging this: #180, #181, #182, #185, #186 and #187.
>> 
>> There are probably a few more testfixes needed to further reduce testing noise.
>
> Christoph Langer has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Use Temurin JDK 11.0.12 for Bootstrap

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:


git checkout 8249095
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

-------------

PR: https://git.openjdk.java.net/jdk11u-dev/pull/189