Some openjdk test targets need to be updated with 'native' tag
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
When you run `_sanity.openjdk.regular` and `_extended.openjdk.regular` the expectation is that it will run test targets that do not require the native test binaries (pointed at via -nativepath option). This is no longer the case likely because new test cases have been added to targets that now expect the native libraries.
We should identify which targets need to be updated with in the [playlist file](https://github.com/adoptium/aqa-tests/blob/master/openjdk/playlist.xml)
```
native
```
Similar as to how we do for functional test material that requires native test binaries in order to run,
https://github.com/eclipse-openj9/openj9/blob/master/test/functional/JLM_Tests/playlist.xml#L253-L255
Contributor guide
Research direction
Start with openjdk/playlist.xml and the _sanity.openjdk.regular and _extended.openjdk.regular targets. Identify test targets that require native binaries, compare their configuration with the linked OpenJ9 playlist example, and mark each applicable target with the native type. Done means those regular runs exclude native-dependent targets unless native binaries are provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100