andygrove opened a new pull request, #7111: URL: https://github.com/apache/datafusion-comet/pull/7111
## Which issue does this PR close? No issue filed. This fixes the Spark 4.1 SQL test failures that evicted #7065, #7059, #6989 and #6370 from the merge queue on 2026-10-19. ## Rationale for this change `setup-spark-builder` restores the Maven repository with the restore-key prefix `Linux-java-maven-`, which picks the newest entry with that prefix. The Delta contrib workflow saved its repository, built with `-Pspark-4.1,delta`, under `Linux-java-maven-<hash>-delta-4.1`. Once that became the newest `java-maven-` entry (saved on main at 07:26 UTC, and by then the only one left), every Spark SQL job restored it. Spark's own Arrow suites then failed in `catalyst`, `sql_core-1` and `sql_core-2` with: ``` No DefaultAllocationManager found on classpath. Can't allocate Arrow buffers. ``` The last passing queue run (#7043) restored the plain `Linux-java-maven-<hash>` entry. Every failing run restored the `-delta-4.1` one. That cache has been deleted to unblock the queue. This PR stops Delta from writing into the shared prefix again. ## What changes are included in this PR? - The Delta contrib jobs save and restore under `Linux-delta-maven-<hash>-<spark>`, so the `java-maven-` fallback used by the other jobs can no longer pick up a Delta repository. - On a miss, the Delta jobs still fall back to `delta-maven-` and then to `java-maven-`, so they keep starting from a warm repository. ## How are these changes tested? `dev/ci/check-ci-config.py` passes. The Delta jobs run nightly or with `run-delta-tests`, so the new key gets exercised on the next nightly run. -- 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]
