Dhruv Chopra

I did launch an internal build yesterday that shows `UpcallThunkGen.cpp` was compiled successfully. However the build didn't complete due to the following issue: ``` 00:52:29 make[10]: *** duping jobs pipe:...

Still seeing the same issue: ``` 14:52:52 20 warnings generated. 14:53:00 java version "21.0.4-internal" 2024-07-16 14:53:00 IBM Semeru Runtime Certified Edition for z/OS (build 21.0.4-internal-adhoc.JENKINS.BuildJDK21s390xzosNightly) 14:53:00 IBM J9 VM (build...

@r30shah Build finally passed so this should be good to merge (URL: view/Nightly/job/Build_JDK21_s390x_zos_Nightly/294/)

> The build referenced above (https://github.com/eclipse-openj9/openj9/pull/20322#issuecomment-2408287911) doesn't seem to have used the changes here (it consumed 8cd5fb6ea9e which I don't see in the history of this pull request); that build...

I'm seeing some infra related errors when trying to build the JDK on Jenkins: ``` Failed fetching commit message from git directory: /jenkins/workspace/Build_JDK21_s390x_zos_Nightly/.git 15:53:51 With the following error: ���z@��������@���@����� ```...

@keithc-ca URLs for internal Jenkins (hyc-runtimes-jenkins) jobs: Here's the build: `view/Nightly/job/Build_JDK21_s390x_zos_Nightly/319/` Here's the tests: `job/Grinder_CR/25682/` The failures are unrelated and documented/explained in runtimes/openj9-openjdk-jdk21-zos/issues/423#issuecomment-93599926

I'll take a look to see if this is related. The test runs with -XX:+CompactStrings already. First step would be to get a failure rate: https://openj9-jenkins.osuosl.org/job/Grinder/2511/ Based on that I'll...

Previous grinder passed. Here's a 100x grinder : https://openj9-jenkins.osuosl.org/job/Grinder/2512/ Also a small 10x grinder on the original failing machine: https://openj9-jenkins.osuosl.org/job/Grinder/2513/

Both grinders passed. Running a final 100x on the original failing machine: https://openj9-jenkins.osuosl.org/job/Grinder/2514/

All grinders passed. Looks like 220 iterations passed with 110 on the same machine that the original failure occurred on. @pshipton what would be the right way to proceed here?...