Hi Oscar, Deleting the Github Actions cache didn't help!
Here are the differences I see: - The AMD64 workflow executes "./build.sh test" while the ARM64 one: "./build.sh clean test". I doubt that the "clean" breaks it - The ARM64 test uses Maven 3.9.4, while the AMD64 one - 3.8.8 and prints this warning: Warning: Cache requires Maven >= 3.9, but version is 3.8.8. Disabling cache. ( https://github.com/apache/avro/actions/runs/6812115807/job/18535403709#step:6:14 ) I could test it tomorrow on a Linux ARM64 VM and double check. Martin On Thu, Nov 9, 2023 at 4:33 PM Oscar Westra van Holthe - Kind < opw...@apache.org> wrote: > Hi all, > > In PR 2513 (https://github.com/apache/avro/pull/2513), most tests > succeed. But the 2nd test in the ARM64 build fails with a compilation > error. > > This means: > > 1. Most builds (including all test & interop builds for Java 8, 11, 17, > 21 & 22-ea) succeed. > 2. For the "Java on Linux ARM64" build, the 1st round of compilation & > test succeeds. > 3. BUT the 2nd round of (for hadoop2) fails with a compilation error in > the Avro code > > > My question: why? > > Any idea where I should start looking? Is it the Maven cache? What could > cause the code being referenced to be different from the code being used? > > > Kind regards, > Oscar > > -- > ✉️ Oscar Westra van Holthe - Kind <opw...@apache.org> > 🌐 https://github.com/opwvhk/ >
