dongjoon-hyun commented on PR #52892: URL: https://github.com/apache/spark/pull/52892#issuecomment-3548435592
Hi, @yaooqinn . This fails again. Given that I don't check all failure log one by one, I believe JitPack failures are more frequent than I report here. In other words, JitPatck.io seems to be a big contributor to the CI flakiness compare to the other infra system. https://github.com/apache/spark/actions/runs/19469862296/job/55714095559 ``` Error: Failed to execute goal on project spark-network-common_2.13: Could not collect dependencies for project org.apache.spark:spark-network-common_2.13:jar:spark-899171 Error: Failed to read artifact descriptor for com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:jar:1.5.3 Error: Caused by: The following artifacts could not be resolved: com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:pom:1.5.3 (absent): Could not transfer artifact com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:pom:1.5.3 from/to jitpack.io (https://jitpack.io/): status code: 500, reason phrase: Internal Server Error (500) ``` As a release manager, I'd like to ask you to revert `JitPatck` compile dependency from Apache Spark 4.1.0, @yaooqinn ? We can keep this in the master branch for Apache Spark 4.2.0. -- 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]
