Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider running jtreg in CI #152

Open
qinsoon opened this issue Apr 12, 2022 · 1 comment
Open

Consider running jtreg in CI #152

qinsoon opened this issue Apr 12, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@qinsoon
Copy link
Member

qinsoon commented Apr 12, 2022

Build and test with jtreg

# build jtreg (clone jtreg)
bash make/build.sh --jdk /usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/

# build openjdk with jtreg
export DEBUG_LEVEL=release && export MMTK_PLAN= && export RUSTUP_TOOLCHAIN=nightly-2022-02-11 && sh configure --disable-warnings-as-errors --with-debug-level=$DEBUG_LEVEL --with-jtreg=/home/yilin/Code/jtreg/build/images/jtreg  && make CONF=linux-x86_64-normal-server-$DEBUG_LEVEL THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk

# build with jtreg native
make build-test-hotspot-jtreg-native CONF=linux-x86_64-normal-server-$DEBUG_LEVEL THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk
make build-test-jdk-jtreg-native CONF=linux-x86_64-normal-server-$DEBUG_LEVEL THIRD_PARTY_HEAP=$PWD/../mmtk-openjdk/openjdk

It generates stuff in 
- build/linux-x86_64-normal-server-release/support/test/hotspot/jtreg/native/lib
- build/linux-x86_64-normal-server-release/support/test/jdk/jtreg/native/

# Run test
JDK_IMAGE_DIR=build/linux-x86_64-normal-server-release/jdk TEST_IMAGE_DIR=build/linux-x86_64-normal-server-release/support/test/ BOOT_JDK=/usr/lib/jvm/adoptopenjdk-11-hotspot-amd64/ JT_HOME=/home/yilin/Code/jtreg/build/images/jtreg make run-test-prebuilt TEST=tier1 JTREG="JAVA_OPTIONS=-XX:+UseThirdPartyHeap -XX:MetaspaceSize=500M

Useful links:

@qinsoon qinsoon added the enhancement New feature or request label Apr 12, 2022
@qinsoon
Copy link
Member Author

qinsoon commented Apr 12, 2022

I ran the test with one of my dev branches. And the results are like below, comparing to running the tests with their stock GC (using the same build but without -XX:+UseThirdPartyHeap).

I probably did not config the test build correct. There are some failures that exist in both runs, which is possibly due to the incorrect test config. We would need to figure it out.

Results with Rust MMTk

==============================
Test summary
==============================
   TEST                                              TOTAL  PASS  FAIL ERROR   
>> jtreg:test/hotspot/jtreg:tier1                     1131   954   175     2 <<
>> jtreg:test/jdk:tier1                               1865  1767    84    14 <<
>> jtreg:test/langtools:tier1                         3910  3898     5     7 <<
   jtreg:test/nashorn:tier1                              0     0     0     0   
   jtreg:test/jaxp:tier1                                 0     0     0     0   
==============================
TEST FAILURE

Results with the stock GC

==============================
Test summary
==============================
   TEST                                              TOTAL  PASS  FAIL ERROR   
>> jtreg:test/hotspot/jtreg:tier1                     1428  1272   156     0 <<
>> jtreg:test/jdk:tier1                               1863  1811    52     0 <<
>> jtreg:test/langtools:tier1                         3911  3905     1     5 <<
   jtreg:test/nashorn:tier1                              0     0     0     0   
   jtreg:test/jaxp:tier1                                 0     0     0     0   
==============================
TEST FAILURE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant