ankithpraveen commented on PR #8634: URL: https://github.com/apache/hadoop/pull/8634#issuecomment-5114711264
Jenkins Build 3 failed after approximately 24 hours with exit code 137. Its JUnit report recorded two timeout failures: 1. TestDFSClientRetries.testLeaseRenewAndDFSOutputStreamDeadLock 2. TestDFSClientRetries.testLeaseRenewSocketTimeout The failure stacks are in HDFS DataStreamer, DFSOutputStream, LeaseRenewer, and test synchronization code. They do not contain any changed Commons API or linkage error. See the [Build #3 test report](https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8634/3/testReport/) and [console](https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-8634/3/consoleText). Further, they pass on local testing. The same commit’s [GitHub Actions HDFS run](https://github.com/ankithpraveen/apache-hadoop/actions/runs/30335185629/job/90200931902) reported 5,266 tests with zero final failures, although the Surefire fork later timed out. Build 2 also passed Maven install, JDK 17/21 compilation, and shaded-client testing, and I only updated the commit message to trigger Build 3. These results do not show a deterministic Commons compatibility failure. Please let me know whether another Jenkins build retrigger is required. @ayushtkn @slfan1989 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
