You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by Oscar Westra van Holthe - Kind <op...@apache.org> on 2023/11/09 14:32:36 UTC
Help wanted: 2nd test in ARM64 build fails
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 <op...@apache.org>
🌐 https://github.com/opwvhk/
Re: Help wanted: 2nd test in ARM64 build fails
Posted by Oscar Westra van Holthe - Kind <os...@westravanholthe.nl>.
--
Oscar Westra van Holthe - Kind <os...@westravanholthe.nl>
On fr 10 nov. 2023 14:04, Martin Grigorov <mg...@apache.org> wrote:
> I've ignored the avro-ipc-jetty Maven module and the build passed!
>
> I also re-triggered the build on main (
> https://github.com/apache/avro/actions/runs/6784706838/job/18554971516)
> and
> all is green too.
>
> I am not sure what the issue is in your branch (and with avro-ipc-jetty)
> but I think you can ignore it for now!
>
Thank you so much!
I'm not sure what the change affected in avro-ipc-jetty... especially as
the symptom was a compile error. But at least I can see if I can keep the
build passing.
Kind regards,
Oscar
Re: Help wanted: 2nd test in ARM64 build fails
Posted by Martin Grigorov <mg...@apache.org>.
I've ignored the avro-ipc-jetty Maven module and the build passed!
I also re-triggered the build on main (
https://github.com/apache/avro/actions/runs/6784706838/job/18554971516) and
all is green too.
I am not sure what the issue is in your branch (and with avro-ipc-jetty)
but I think you can ignore it for now!
On Fri, Nov 10, 2023 at 2:56 PM Martin Grigorov <mg...@apache.org>
wrote:
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary for Apache Avro Java 1.12.0-SNAPSHOT:
> [INFO]
> [INFO] Apache Avro Java ................................... SUCCESS [
> 0.116 s]
> [INFO] Apache Avro ........................................ SUCCESS [01:03
> min]
> [INFO] Apache Avro Android Compatibility .................. SUCCESS [
> 1.181 s]
> [INFO] Apache Avro IDL .................................... SUCCESS [
> 52.651 s]
> [INFO] Apache Avro Compiler ............................... SUCCESS [
> 42.407 s]
> [INFO] Apache Avro Maven Plugin ........................... SUCCESS [
> 25.477 s]
> [INFO] Apache Avro IPC .................................... SUCCESS [
> 47.778 s]
> [INFO] Apache Avro IPC Jetty .............................. FAILURE [
> 1.646 s]
> [INFO] Apache Avro IPC Netty .............................. SKIPPED
> [INFO] Trevni Java ........................................ SKIPPED
> [INFO] Trevni Java Core ................................... SKIPPED
> [INFO] Apache Avro Mapred API ............................. SKIPPED
> [INFO] Trevni Java Avro ................................... SKIPPED
> [INFO] Trevni Specification ............................... SKIPPED
> [INFO] Apache Avro Tools .................................. SKIPPED
> [INFO] Apache Avro Protobuf Compatibility ................. SKIPPED
> [INFO] Apache Avro Thrift Compatibility ................... SKIPPED
> [INFO] Apache Avro Maven Archetypes ....................... SKIPPED
> [INFO] Apache Avro Maven Service Archetype ................ SKIPPED
> [INFO] Apache Avro gRPC ................................... SKIPPED
> [INFO] Avro Integration Tests ............................. SKIPPED
> [INFO] Apache Avro Codegen Test dependencies .............. SKIPPED
> [INFO] Apache Avro Codegen Test ........................... SKIPPED
> [INFO] Apache Avro Performance Test Suite ................. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 03:55 min
> [INFO] Finished at: 2023-11-10T12:42:53Z
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.1.0:test (default-test) on
> project avro-ipc-jetty: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:3.1.0:test failed:
> org.junit.platform.commons.JUnitException: TestEngine with ID
> 'junit-jupiter' failed to discover tests: ClassSelector [className =
> 'org.apache.avro.ipc.jetty.TestStatsPluginAndServlet', classLoader = null]
> resolution failed: failed to access class
> org.apache.avro.ipc.stats.Histogram from class
> org.apache.avro.ipc.jetty.TestStatsPluginAndServlet
> (org.apache.avro.ipc.stats.Histogram and
> org.apache.avro.ipc.jetty.TestStatsPluginAndServlet are in unnamed module
> of loader org.apache.maven.surefire.booter.IsolatedClassLoader @764d64dc)
> -> [Help 1]
>
>
> It is a fresh VM with :
>
> $ java --version
> openjdk 11.0.20 2023-07-18
> OpenJDK Runtime Environment Bisheng (build 11.0.20+8)
>
> $ mvn --version
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /home/mgrigorov/git/apache/avro/apache-maven-3.9.4
> Java version: 11.0.20, vendor: Bisheng, runtime:
> /usr/lib/jvm/java-11-openjdk-11.0.20.8-0.oe2203.aarch64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.10.0-60.74.0.98.oe2203.aarch64", arch:
> "aarch64", family: "unix"
>
>
> On Thu, Nov 9, 2023 at 8:39 PM Martin Grigorov <mg...@apache.org>
> wrote:
>
>> 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 <
>> opwvhk@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 <op...@apache.org>
>>> 🌐 https://github.com/opwvhk/
>>>
>>
Re: Help wanted: 2nd test in ARM64 build fails
Posted by Martin Grigorov <mg...@apache.org>.
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Avro Java 1.12.0-SNAPSHOT:
[INFO]
[INFO] Apache Avro Java ................................... SUCCESS [
0.116 s]
[INFO] Apache Avro ........................................ SUCCESS [01:03
min]
[INFO] Apache Avro Android Compatibility .................. SUCCESS [
1.181 s]
[INFO] Apache Avro IDL .................................... SUCCESS [
52.651 s]
[INFO] Apache Avro Compiler ............................... SUCCESS [
42.407 s]
[INFO] Apache Avro Maven Plugin ........................... SUCCESS [
25.477 s]
[INFO] Apache Avro IPC .................................... SUCCESS [
47.778 s]
[INFO] Apache Avro IPC Jetty .............................. FAILURE [
1.646 s]
[INFO] Apache Avro IPC Netty .............................. SKIPPED
[INFO] Trevni Java ........................................ SKIPPED
[INFO] Trevni Java Core ................................... SKIPPED
[INFO] Apache Avro Mapred API ............................. SKIPPED
[INFO] Trevni Java Avro ................................... SKIPPED
[INFO] Trevni Specification ............................... SKIPPED
[INFO] Apache Avro Tools .................................. SKIPPED
[INFO] Apache Avro Protobuf Compatibility ................. SKIPPED
[INFO] Apache Avro Thrift Compatibility ................... SKIPPED
[INFO] Apache Avro Maven Archetypes ....................... SKIPPED
[INFO] Apache Avro Maven Service Archetype ................ SKIPPED
[INFO] Apache Avro gRPC ................................... SKIPPED
[INFO] Avro Integration Tests ............................. SKIPPED
[INFO] Apache Avro Codegen Test dependencies .............. SKIPPED
[INFO] Apache Avro Codegen Test ........................... SKIPPED
[INFO] Apache Avro Performance Test Suite ................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 03:55 min
[INFO] Finished at: 2023-11-10T12:42:53Z
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.1.0:test (default-test) on
project avro-ipc-jetty: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:3.1.0:test failed:
org.junit.platform.commons.JUnitException: TestEngine with ID
'junit-jupiter' failed to discover tests: ClassSelector [className =
'org.apache.avro.ipc.jetty.TestStatsPluginAndServlet', classLoader = null]
resolution failed: failed to access class
org.apache.avro.ipc.stats.Histogram from class
org.apache.avro.ipc.jetty.TestStatsPluginAndServlet
(org.apache.avro.ipc.stats.Histogram and
org.apache.avro.ipc.jetty.TestStatsPluginAndServlet are in unnamed module
of loader org.apache.maven.surefire.booter.IsolatedClassLoader @764d64dc)
-> [Help 1]
It is a fresh VM with :
$ java --version
openjdk 11.0.20 2023-07-18
OpenJDK Runtime Environment Bisheng (build 11.0.20+8)
$ mvn --version
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /home/mgrigorov/git/apache/avro/apache-maven-3.9.4
Java version: 11.0.20, vendor: Bisheng, runtime:
/usr/lib/jvm/java-11-openjdk-11.0.20.8-0.oe2203.aarch64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.10.0-60.74.0.98.oe2203.aarch64", arch:
"aarch64", family: "unix"
On Thu, Nov 9, 2023 at 8:39 PM Martin Grigorov <mg...@apache.org> wrote:
> 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 <
> opwvhk@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 <op...@apache.org>
>> 🌐 https://github.com/opwvhk/
>>
>
Re: Help wanted: 2nd test in ARM64 build fails
Posted by Martin Grigorov <mg...@apache.org>.
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 <
opwvhk@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 <op...@apache.org>
> 🌐 https://github.com/opwvhk/
>