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

Fix build on Apache s390x Jenkins slave #13161

Closed
uschindler opened this issue Mar 6, 2024 · 7 comments
Closed

Fix build on Apache s390x Jenkins slave #13161

uschindler opened this issue Mar 6, 2024 · 7 comments

Comments

@uschindler
Copy link
Contributor

Description

See https://issues.apache.org/jira/browse/LCN4C-9:

Apache Lucene CI is disabled for s390x recently on 29th Feb. Couldn't find any specific reasons why it's disabled.

https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main%20(s390x%20big%20endian)/

Can you please check and let us know if anything is needed.

Version and environment details

No response

@uschindler uschindler self-assigned this Mar 6, 2024
@uschindler
Copy link
Contributor Author

We need Java 21 now, which may not be installed on that machine, so I disabled it while switching Jenkins jobs- I can quickly fix thus. If you tell me which Java 21 setup we can use for Apache Lucene main tests, I can reenable the job. Is selecting "Latest Java 21" working on that slave node?

Sorry for not making progress here, I just quickly disabled it to setup jobs. Will try in a moment.

@uschindler
Copy link
Contributor Author

Quick feedback: Yes it does not work with Java 21:

[Lucene-Check-main (s390x big endian)] $ "/home/jenkins/jenkins-home/712657a4/workspace/Lucene/Lucene-Check-main (s390x big endian)/gradlew" -Dtests.haltonfailure=false -Dtests.badapples=false --continue check

ERROR: JAVA_HOME is set to an invalid directory: /home/jenkins/tools/java/latest21

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
[Email-ext] Notification email body length: 696
Sending email to: builds@lucene.apache.org
Finished: FAILURE

@uschindler
Copy link
Contributor Author

CC @Nayana-ibm

@uschindler uschindler added this to the 10.0.0 milestone Mar 6, 2024
@uschindler uschindler changed the title Fix build on Apache s390 Jenkins slave Fix build on Apache s390x Jenkins slave Mar 6, 2024
@Nayana-ibm
Copy link

@uschindler I have created an issue to install Java 21 on s390x nodes
https://issues.apache.org/jira/browse/INFRA-25589

@uschindler
Copy link
Contributor Author

I disabled both failing jobs until the INFRA ticket is resolved. Please ping me if you have updates.

@Nayana-ibm
Copy link

Nayana-ibm commented Apr 1, 2024

Apache Lucene builds are passing now.
https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main%20(s390x%20big%20endian)/

https://issues.apache.org/jira/browse/INFRA-25589 is still open for installing Openjdk 21 or hotspot

@uschindler
Copy link
Contributor Author

Thanks all fine.

It would be nice to get a feedback by Infra. I am tempted to install a fake job to just print version information.

Uwe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants