The tests runs the jtreg and the AdoptOpenjdk test, but I want to run AdoptOpenjdk tests only. Is there a way for me to accomplish this?
thanks :)
jtreg tests are categorized in a group called
other tests we run at the project are categorized into the following groups:
system
perf
functional
external
You can choose to run each one of those groups individually. Which set are you interested in running?
If you want to run the system tests, you would use TARGET=system or TARGET=sanity.system (to run just the ones in that group that are tagged as sanity tests).
Some additional doc here: https://github.com/eclipse/openj9/wiki/Reproducing-Test-Failures-Locally
I'm interested in AdoptOpenJDK tests only
Ok I can interpret your request 2 ways, but I think you want the 1st option below:
1) To run test material that is hosted 'in AdoptOpenJDK repos':
2) To run the test material that 'AdoptOpenJDK runs' to verify their binaries:
In other words, AdoptOpenJDK uses test material from a variety of locations to verify its binaries. More details here: https://medium.com/adoptopenjdk/the-first-drop-introducing-adoptopenjdk-quality-assurance-aqa-v1-0-fe09f10ced80
So, the steps to run the system tests (or see instructions here):
export TEST_JDK_HOME=/locationOfJDKUnderTest
git clone https://github.com/AdoptOpenJDK/openjdk-tests.git (to /testLocation)
cd openjdk-tests
./get.sh -t /testLocation/openjdk-tests
cd TestConfig
export BUILD_LIST=system
make -f run_configure.mk
make compile
make _sanity.system
I set $BUILD_LIST and then make -f run_configure but when I run make compile I have this issue:
get-source:
[exec] Didn't find password for CVSROOT ':pserver:[email protected]:/cvs/mauve'.
Do you know how can I fix it? @smlambert
Perhaps we can connect tomorrow via AdoptOpenJDK Slack #testing channel, and step through it.
alternatively please share the full output of your compile step, and please share printenv output, so I can see if there are env vars that are set but wrong.
I will verify tonight that the instructions I shared work locally on my machine.
You can also see the console output of a Grinder job that runs sanity.system target to see the commands that are run to achieve it:
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/961/consoleFull
I have verified the instructions shared to run system tests locally. I also captured the steps in a 1 minute recording. If you follow those steps without variance and still are unable to run the system tests, please re-open this issue (and share output of printenv to see what may be running interference).
yeah, it already works :) thanks for your help
Most helpful comment
Ok I can interpret your request 2 ways, but I think you want the 1st option below:
1) To run test material that is hosted 'in AdoptOpenJDK repos':
2) To run the test material that 'AdoptOpenJDK runs' to verify their binaries:
In other words, AdoptOpenJDK uses test material from a variety of locations to verify its binaries. More details here: https://medium.com/adoptopenjdk/the-first-drop-introducing-adoptopenjdk-quality-assurance-aqa-v1-0-fe09f10ced80
So, the steps to run the system tests (or see instructions here):
export TEST_JDK_HOME=/locationOfJDKUnderTest
git clone https://github.com/AdoptOpenJDK/openjdk-tests.git (to /testLocation)
cd openjdk-tests
./get.sh -t /testLocation/openjdk-tests
cd TestConfig
export BUILD_LIST=system
make -f run_configure.mk
make compile
make _sanity.system