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

Verify initial Trestle pipelines against real-world examples of upstream PRs #5137

Open
smlambert opened this issue Mar 12, 2024 · 2 comments
Assignees
Labels
triage required Issue needs deeper triage to determine which repo to move issue into

Comments

@smlambert
Copy link
Contributor

smlambert commented Mar 12, 2024

Related to adoptium/ci-jenkins-pipelines#895 (see also https://github.com/adoptium/ci-jenkins-pipelines/wiki/Trestle-Initiative), we will test various use cases to validate the final feature set that the Trestle pipelines should deliver.

Trestle Coverage Upstream branch Link(s) to results Notes
Support JDK8
Support JDK11
Support JDK17 PR Grid comment
Support JDK21
Support Tip (JDK23 atm)
Trestle Feature Verify works as planned
Build 3 variants (release|fast-debug|slow-debug)
Trigger correct test sets
Builds on expected nodes
Displays properly in TRSS
Discards artifacts after X days
Access control for pipeline works
Rerun failed tests in Grinder works
Easy to find RELEASE INFO & Build Metadata
@smlambert smlambert self-assigned this Mar 12, 2024
@smlambert smlambert added the triage required Issue needs deeper triage to determine which repo to move issue into label Mar 13, 2024
@smlambert
Copy link
Contributor Author

smlambert commented Mar 14, 2024

JDK17 triage notes

-r https://github.com/Delawen/jdk17u-dev -b backport-JDK-8280377 --disable-adopt-branch-safety

sanity.openjdk == most tier1 tests, 5058 testcases
extended.openjdk == most tier2, tier3 and tier4 tests, 12,633 testcases

For details on how to navigate and understand what tests are included from the OpenJDK project and run as part of the AQAvit tests, please see How-OpenJDK-tests-map-to-AQAvit-test-targets.

✔️ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸️ means activity not yet started.

Platform Status Notes
aarch64_linux ✔️ 1 fail, 17690 pass, likely machine config issue* assertion using missing sleep command
aarch64_mac ⏸️ Smoke tests failed, so no other testing triggered, needs investigation
ppc64_aix ✔️ 2 testcases fail, machine issue** out of memory
ppc64le_linux ✔️ All pass
s390x_linux
x86-64_alpine-linux ✔️ All pass
x86-64_linux
x86-64_mac ✔️ All pass
x86-64_windows ✔️ failures specific to test-ibmcloud-win2012r2-x64-2 node, and pass when rerun on test-azure-win2019-x64-1
  • aarch64_linux - InfoTest.test3 failure, expecting sleep command, machine issue (on test-docker-centos8-armv8-1)
18:01:55  test InfoTest.test3(): failure
18:01:55  java.lang.AssertionError: Command: expected: 'sleep', actual: /usr/bin/coreutils expected [true] but found [false]
18:01:55  	at org.testng.Assert.fail(Assert.java:99)
18:01:55  	at org.testng.Assert.failNotEquals(Assert.java:1037)
18:01:55  	at org.testng.Assert.assertTrue(Assert.java:45)
18:01:55  	at InfoTest.test3(InfoTest.java:302)

** ppc64_aix - StreamingBody and ThreadStartTest fail with out of memory issues on test-osuosl-aix72-ppc64-5

java/net/httpclient/StreamingBody.java
...
iteration: 76
03:27:10  [47.812s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (11=EAGAIN) for attributes: stacksize: 2112k, guardsize: 0k, detached.
03:27:10  [47.812s][warning][os,thread] Failed to start the native thread for java.lang.Thread "HttpClient-377-SelectorManager"
03:27:10  test StreamingBody.test("https://127.0.0.1:58465/https2/streamingbody/z"): failure
03:27:10  java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
03:27:10  	at java.base/java.lang.Thread.start0(Native Method)
03:27:10  	at java.base/java.lang.Thread.start(Thread.java:809)
03:27:10  	at java.net.http/jdk.internal.net.http.HttpClientImpl.start(HttpClientImpl.java:337)
03:27:10  	at java.net.http/jdk.internal.net.http.HttpClientImpl.create(HttpClientImpl.java:271)
03:27:10  	at java.net.http/jdk.internal.net.http.HttpClientBuilderImpl.build(HttpClientBuilderImpl.java:135)
03:27:10  	at StreamingBody.test(StreamingBody.java:102)


javax/management/mxbean/ThreadStartTest.java
05:44:38  STDOUT:
05:44:38  [0.312s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (11=EAGAIN) for attributes: stacksize: 2112k, guardsize: 0k, detached.
05:44:38  [0.312s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Thread-911"
05:44:38  STDERR:
05:44:38  java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
05:44:38  	at java.base/java.lang.Thread.start0(Native Method)
05:44:38  	at java.base/java.lang.Thread.start(Thread.java:809)
05:44:38  	at ThreadStartTest.main(ThreadStartTest.java:53)
05:44:38  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
05:44:38  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
05:44:38  	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
05:44:38  	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
05:44:38  	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
05:44:38  	at java.base/java.lang.Thread.run(Thread.java:840)

...

Example of new test added via the upstream PR running in this Jenkins job:
Grinder/9156 scratch that, will need a PR to aqa-tests to support this case (new tests coming in from an upstream PR, instead of pulling from merged material from the mirror repository.

@smlambert
Copy link
Contributor Author

JDK17 s390x_linux triage

Machine related failures: Cannot run program "hostname": error=2, No such file or directory on test-docker-sles12-s390x-1

java.lang.RuntimeException: Get hostname failed.
	at PostThruProxyWithAuth.getHostname(PostThruProxyWithAuth.java:263)
	at PostThruProxyWithAuth.doClientSide(PostThruProxyWithAuth.java:180)
	at PostThruProxyWithAuth.main(PostThruProxyWithAuth.java:126)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.io.IOException: Cannot run program "hostname": error=2, No such file or directory
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:569)
	at jdk.test.lib.process.ProcessTools.privilegedStart(ProcessTools.java:611)
	at jdk.test.lib.process.ProcessTools.executeProcess(ProcessTools.java:442)
	at jdk.test.lib.process.ProcessTools.executeProcess(ProcessTools.java:421)
	at jdk.test.lib.process.ProcessTools.executeProcess(ProcessTools.java:408)
	at jdk.test.lib.process.ProcessTools.executeProcess(ProcessTools.java:489)
	at jdk.test.lib.process.ProcessTools.executeCommand(ProcessTools.java:537)
	at PostThruProxyWithAuth.getHostname(PostThruProxyWithAuth.java:260)
	... 8 more
Caused by: java.io.IOException: error=2, No such file or directory
	at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
	at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:314)
	at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244)
	at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
	... 17 more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage required Issue needs deeper triage to determine which repo to move issue into
Projects
Status: In Progress
Development

No branches or pull requests

1 participant