hutiefang76 commented on PR #4427: URL: https://github.com/apache/amoro/pull/4427#issuecomment-6065428118
CI follow-up for head `e6eff1d`: the [JDK 17 / Spark 3.5 job](https://github.com/apache/amoro/actions/runs/37594068852/job/112702272994) failed during `./mvnw validate` at Maven wrapper SHA-256 validation, before Maven compilation or tests. Three JDK 11 legs were cancelled after that failure, consistent with the matrix's default fail-fast behavior; the Hadoop 2 and Trino runs on the same head passed. I checked the [official Maven wrapper 3.3.4 artifact](https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.3.4/maven-wrapper-3.3.4.jar): HTTP 200, 63,093 bytes, SHA-256 `4e2fbf6554bc8a4702cdfdd3bef464f423393d784ddbb037216320ce55d5e4e1`, exactly matching `wrapperSha256Sum`. Its published SHA-1 also matches. `mvnw`, `mvnw.cmd` and the wrapper properties are byte-identical between this PR and master at `2c85dcb`; the local wrapper jar matches the official SHA-256 too. On the unchanged PR head, `./mvnw validate` passed locally and all 5 `TestHiveSchemaUtil` tests passed on JDK 17. These local results do not establish a full remote CI pass. The failed runner's downloaded jar is unavailable, so the bootstrap failure's underlying cause remains unconfirmed. I attempted a targeted rerun, but the Actions API returned HTTP 403: repository administrator rights are required. Could a maintainer rerun the failed and cancelled legs? I have kept the wrapper integrity checks unchanged. -- 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]
