adoptium / adoptium/infrastructure

Add template for tests on new platform/distribution environments

Open
#3,600 1 comment 0 reactions 0 assignees View on GitHub
doc
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

As per https://github.com/adoptium/infrastructure/blob/master/FAQ.md#adding-new-systems we have a process whereby new types of machines (New OS versions, new distributions etc.) Are run through an AQA_Test_Pipeline run.

It would be good if we had a standard template for logging the results of this e.g.

Key:
- ✅ - All test cases pass
- ⚠️ - Test suite had failures, but they are all covered by existing issues
- ❌ - New unexpected (or untracked) failures which are of concern as they may indicate issues with this combination

## Ubuntu 24.04 / JDK17 / aarch64

Test suite | Result ✅⚠️❌
---|---
[sanity.functional](https://ci.adoptium.net/job/Test_openjdk22_hs_sanity.functional_aarch64_linux/) | ✅
extended.functional | ✅
special.functional | ❌ (List of failing cases + link to new issue)
sanity.openjdk | ⚠️ (IssueLink1, Issuelink2)
extended.openjdk | ❌ (List of:failing cases + link to new issue/s)
sanity.system |
extended.system |
sanity.perf |
extended.perf |

The table could be extended with other columns if desired / appropriate e.g.

## Ubuntu 24.04

Test suite | JDK | Arch | Result ✅⚠️❌
---|---|---|---
sanity.openjdk | 17 | riscv64| ✅
extended.openjdk | 17 | riscv64 | ❌ (New failing issue links)
sanity.openjdk | 21 | riscv64| ✅
extended.openjdk | 21 | riscv64 | ❌ (New failing issue links)
sanity.openjdk | 8 | riscv64| ⚠️ (IssueLink1, Issuelink2)
extended.openjdk | 8 | riscv64 | ❌ (New failing issue links)

Contributor guide

Open the contributing guide

Research direction

Read the FAQ section on adding new systems and review the repository for existing templates related to AQA_Test_Pipeline results. The finished template should consistently capture the platform, JDK, architecture, test suites, result symbols, failing cases, and links to related issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, ubuntu
Domain
infrastructure, testing
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.