Help needed with maven-invoker builds

[Markku Korkeala]

Hi all,

in F37 release cycle maven-invoker builds started to fail [1], for example:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458 .

The reason is that two tests fail:

[ERROR] DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but was:<-2147483648>
[ERROR] DefaultInvokerTest.testSpaceProperties:218 expected:<0> but was:<-2147483648>

https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log

I haven't made any changes, the same version built fine in F36 release
cycle, so I dont think its JDK17 related, possible some other dependency
is updated which results in the error.

I was able to add some debugging and logging, at least the first test gets exception:
org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.

After debugging this I havent found any solution, seems my option are:

1. Disable the two tests, but some other application might brake
2. Orphan maven-invoker

So any help is appreciated.

1: https://koji.fedoraproject.org/koji/packageinfo?packageID=15295
2: https://src.fedoraproject.org/rpms/maven-invoker

Best regards,
Markku Korkeala

[Marián Konček]

I tried to see whether an update to maven-invoker 3.2.0 would fix the 
problem but now there are 3 test failures:

[ERROR] Failures:
[ERROR]   DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but 
was:<-2147483648>
[ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268 expected:<0> 
but was:<126>
[ERROR]   DefaultInvokerTest.testSpaceProperties:218 expected:<0> but 
was:<-2147483648>

I will try to inspect it further.

On 28. 7. 2022 13:55, Markku Korkeala wrote:
> Hi all,
>
> in F37 release cycle maven-invoker builds started to fail [1], for example:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458  .
>
> The reason is that two tests fail:
>
> [ERROR] DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but was:<-2147483648>
> [ERROR] DefaultInvokerTest.testSpaceProperties:218 expected:<0> but was:<-2147483648>
>
> https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log
>
> I haven't made any changes, the same version built fine in F36 release
> cycle, so I dont think its JDK17 related, possible some other dependency
> is updated which results in the error.
>
> I was able to add some debugging and logging, at least the first test gets exception:
> org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.
>
> After debugging this I havent found any solution, seems my option are:
> Disable the two tests, but some other application might brake
> Orphan maven-invoker
>
> So any help is appreciated.
>
> 1:https://koji.fedoraproject.org/koji/packageinfo?packageID=15295
> 2:https://src.fedoraproject.org/rpms/maven-invoker
>
> Best regards,
> Markku Korkeala
> _______________________________________________
> java-devel mailing list [e-mail]
> To unsubscribe send an email [e-mail]
> Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:https://lists.fedoraproject.org/archives/list/[e-mail]...
> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

[Stephen Snow]

I get this error when I try to build it locally ...
[ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268 expected:<0>
but was:<126>
I'll try to investigate further.

Stephen

On Thu, 2022-07-28 at 16:30 +0200, Marián Konček wrote:
> I tried to see whether an update to maven-invoker 3.2.0 would fix the
> problem but now there are 3 test failures:
> [ERROR] Failures:  
> [ERROR]   DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0>
> but was:<-2147483648> 
> [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268
> expected:<0> but was:<126> 
> [ERROR]   DefaultInvokerTest.testSpaceProperties:218 expected:<0> but
> was:<-2147483648> 
> I will try to inspect it further.
> On 28. 7. 2022 13:55, Markku Korkeala wrote:
> > Hi all,
> >
> > in F37 release cycle maven-invoker builds started to fail [1], for example:
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458 .
> >
> > The reason is that two tests fail:
> >
> > [ERROR] DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but was:<-2147483648>
> > [ERROR] DefaultInvokerTest.testSpaceProperties:218 expected:<0> but was:<-2147483648>
> >
> > https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log
> >
> > I haven't made any changes, the same version built fine in F36 release
> > cycle, so I dont think its JDK17 related, possible some other dependency
> > is updated which results in the error.
> >
> > I was able to add some debugging and logging, at least the first test gets exception:
> > org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.
> >
> > After debugging this I havent found any solution, seems my option are:
> > Disable the two tests, but some other application might brake
> > Orphan maven-invoker
> >
> > So any help is appreciated.
> >
> > 1: https://koji.fedoraproject.org/koji/packageinfo?packageID=15295
> > 2: https://src.fedoraproject.org/rpms/maven-invoker
> >
> > Best regards,
> > Markku Korkeala
> > _______________________________________________
> > java-devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]...
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
> java-devel mailing list -- [e-mail]
> To unsubscribe send an email to 
> [e-mail]
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]
> aproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

"3.7.5 Exit Status" "If a command is found   but is not executable,
the return status is 126."
$ ls -l ./src/test/resources/test-maven-wrapper-in-project/mvnw
-rw-r--r--. 1 whitingjr whitingjr 984 Jul 28 22:31
./src/test/resources/test-maven-wrapper-in-project/mvnw
$ chmod +x ./src/test/resources/test-maven-wrapper-in-project/mvnw$
mvn verify...[INFO] Tests run: 100, Failures: 0, Errors: 0, Skipped: 0
...
Both F35 and F36 tested using JSE 17. Can't explain though what causes
the Integer.MIN_VALUE

Jeremy

On 28/07/2022 at 5:54 PM, "Stephen Snow"  wrote:           I get this
error when I try to build it locally ...[ERROR]  
DefaultInvokerTest.testMavenWrapperInProject:268 expected: but
was:I'll try to investigate further.
Stephen
On Thu, 2022-07-28 at 16:30 +0200, Marián Konček wrote:

I tried to see whether an update to maven-invoker 3.2.0 would fix the
problem but now there are 3 test failures:

[ERROR] Failures:  
 [ERROR]   DefaultInvokerTest.testBuildShouldSucceed:56 expected: but
was: 
 [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268 expected:
but was: 
 [ERROR]   DefaultInvokerTest.testSpaceProperties:218 expected: but
was: 
    I will try to inspect it further.
 On 28. 7. 2022 13:55, Markku Korkeala wrote:
    Hi all,
    in F37 release cycle maven-invoker builds started to fail [1], for
example:

https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458 .
    The reason is that two tests fail:
    [ERROR] DefaultInvokerTest.testBuildShouldSucceed:56 expected: but
was:

[ERROR] DefaultInvokerTest.testSpaceProperties:218 expected: but was:
    https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log
    I haven't made any changes, the same version built fine in F36
release

cycle, so I dont think its JDK17 related, possible some other
dependency

is updated which results in the error.
    I was able to add some debugging and logging, at least the first test
gets exception:

org.apache.maven.shared.utils.cli.CommandLineException:  Failure
processing stdout.
    After debugging this I havent found any solution, seems my option
are:
    1. Disable the two tests, but some other application might brake

2. Orphan maven-invoker
    So any help is appreciated.
    1: https://koji.fedoraproject.org/koji/packageinfo?packageID=15295

2: https://src.fedoraproject.org/rpms/maven-invoker
    Best regards,

Markku Korkeala

_______________________________________________

java-devel mailing list -- [e-mail]

To unsubscribe send an email to
[e-mail]

Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/

List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines

List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]...

Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure

_______________________________________________
    java-devel mailing list -- [e-mail]
    To unsubscribe send an email to
[e-mail]
    Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
    List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
    List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]...
    Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure

[Stephen Snow]

Thanks,
It builds locally for me on F36. Tomorrow if I get a chance I'll do a
local mock build of the package.

Stephen

On Thu, 2022-07-28 at 22:52 +0100, [e-mail]
wrote:
> "3.7.5 Exit Status" "If a command is found but is not executable, the
> return status is 126."
>
> $ ls -l ./src/test/resources/test-maven-wrapper-in-project/mvnw
> -rw-r--r--. 1 whitingjr whitingjr 984 Jul 28 22:31
> ./src/test/resources/test-maven-wrapper-in-project/mvnw
> $ chmod +x ./src/test/resources/test-maven-wrapper-in-project/mvnw
> $ mvn verify
> ...
> [INFO] Tests run: 100, Failures: 0, Errors: 0, Skipped: 0
> ...
>
> Both F35 and F36 tested using JSE 17. Can't explain though what
> causes the Integer.MIN_VALUE
>
> Jeremy
>
> On 28/07/2022 at 5:54 PM, "Stephen Snow"  wrote:
> > I get this error when I try to build it locally ...
> > [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268
> > expected:<0> but was:<126>
> > I'll try to investigate further.
> >
> > Stephen
> >
> > On Thu, 2022-07-28 at 16:30 +0200, Marián Konček wrote:
> > > I tried to see whether an update to maven-invoker 3.2.0 would fix
> > > the problem but now there are 3 test failures:
> > > [ERROR] Failures:  
> > > [ERROR]   DefaultInvokerTest.testBuildShouldSucceed:56
> > > expected:<0> but was:<-2147483648> 
> > > [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268
> > > expected:<0> but was:<126> 
> > > [ERROR]   DefaultInvokerTest.testSpaceProperties:218 expected:<0>
> > > but was:<-2147483648> 
> > > I will try to inspect it further.
> > > On 28. 7. 2022 13:55, Markku Korkeala wrote:
> > > > Hi all,
> > > >
> > > > in F37 release cycle maven-invoker builds started to fail [1],
>
> for example:
> > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458 .
> > > >
> > > > The reason is that two tests fail:
> > > >
> > > > [ERROR] DefaultInvokerTest.testBuildShouldSucceed:56
>
> expected:<0> but was:<-2147483648>
> > > > [ERROR] DefaultInvokerTest.testSpaceProperties:218 expected:<0>
>
> but was:<-2147483648>
> > > >
>
> https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log
> > > > I haven't made any changes, the same version built fine in F36
>
> release
> > > > cycle, so I dont think its JDK17 related, possible some other
>
> dependency
> > > > is updated which results in the error.
> > > >
> > > > I was able to add some debugging and logging, at least the
>
> first test gets exception:
> > > > org.apache.maven.shared.utils.cli.CommandLineException: Failure
>
> processing stdout.
> > > > After debugging this I havent found any solution, seems my
>
> option are:
> > > > Disable the two tests, but some other application might
>
> brake
> > > > Orphan maven-invoker
> > > >
> > > > So any help is appreciated.
> > > >
> > > > 1:
>
> https://koji.fedoraproject.org/koji/packageinfo?packageID=15295
> > > > 2: https://src.fedoraproject.org/rpms/maven-invoker
> > > >
> > > > Best regards,
> > > > Markku Korkeala
> > > > _______________________________________________
> > > > java-devel mailing list -- [e-mail]
> > > > To unsubscribe send an email to
>
> [e-mail]
> > > > Fedora Code of Conduct:
>
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > List Guidelines:
>
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]...
> > > > Do not reply to spam on the list, report it:
>
> https://pagure.io/fedora-infrastructure
> > > java-devel mailing list -- [e-mail]
> > > To unsubscribe send an email to 
> > > [e-mail]
> > > Fedora Code of Conduct: 
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: 
> > > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: 
> > > https://lists.fedoraproject.org/archives/list/java-devel@lists.f
> > > edoraproject.org
> > > Do not reply to spam on the list, report it: 
> > > https://pagure.io/fedora-infrastructure

[Markku Korkeala]

Hi,

thanks all for the replies, I was running for the same issues with 3.2.0 version as well,
good to see that return code 126 is fixable. Like I wrote in the opening message, I was
able to add some debug messages and see that in the first case of Integer.MIN_VALUE return
code, the exception returned from the process was:
org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.

(the test sends InvocationRequest and receives InvocationResponse, the response has
the Exception and return code).

But haven't got any deeper than that, what is the actual cause for the error.

Best regards.
Markku Korkeala

On 7/29/22 00:52, [e-mail] wrote:
> "3.7.5 Exit Status" "If a command is found but is not executable, the return status is 126."
>
> $ ls -l ./src/test/resources/test-maven-wrapper-in-project/mvnw
> -rw-r--r--. 1 whitingjr whitingjr 984 Jul 28 22:31
> ./src/test/resources/test-maven-wrapper-in-project/mvnw
> $ chmod +x ./src/test/resources/test-maven-wrapper-in-project/mvnw
> $ mvn verify
> ...
> [INFO] Tests run: 100, Failures: 0, Errors: 0, Skipped: 0
> ...
>
> Both F35 and F36 tested using JSE 17. Can't explain though what causes the Integer.MIN_VALUE
>
> Jeremy
>
> On 28/07/2022 at 5:54 PM, "Stephen Snow"  wrote:
> I get this error when I try to build it locally ...
> [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268 expected:<0> but was:<126>
> I'll try to investigate further.
>
> Stephen
>
> On Thu, 2022-07-28 at 16:30 +0200, Marián Konček wrote:
>
>     I tried to see whether an update to maven-invoker 3.2.0 would fix the problem but
>     now there are 3 test failures:
>
>     [ERROR] Failures:  
>     [ERROR]   DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but
>     was:<-2147483648>
>     [ERROR]   DefaultInvokerTest.testMavenWrapperInProject:268 expected:<0> but was:<126>
>     [ERROR]   DefaultInvokerTest.testSpaceProperties:218 expected:<0> but
>     was:<-2147483648>
>
>     I will try to inspect it further.
>
>     On 28. 7. 2022 13:55, Markku Korkeala wrote:
>
>         Hi all,
>
>
>         in F37 release cycle maven-invoker builds started to fail [1], for example:
>
>         https://koji.fedoraproject.org/koji/buildinfo?buildID=2015458 .
>
>
>         The reason is that two tests fail:
>
>
>         [ERROR] DefaultInvokerTest.testBuildShouldSucceed:56 expected:<0> but was:<-2147483648>
>
>         [ERROR] DefaultInvokerTest.testSpaceProperties:218 expected:<0> but was:<-2147483648>
>
>
>         https://kojipkgs.fedoraproject.org//work/tasks/8915/89828915/build.log
>
>
>         I haven't made any changes, the same version built fine in F36 release
>
>         cycle, so I dont think its JDK17 related, possible some other dependency
>
>         is updated which results in the error.
>
>
>         I was able to add some debugging and logging, at least the first test gets exception:
>
>         org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.
>
>
>         After debugging this I havent found any solution, seems my option are:
>
>
>         1. Disable the two tests, but some other application might brake
>
>         2. Orphan maven-invoker
>
>
>         So any help is appreciated.
>
>
>         1: https://koji.fedoraproject.org/koji/packageinfo?packageID=15295
>
>         2: https://src.fedoraproject.org/rpms/maven-invoker
>
>
>         Best regards,
>
>         Markku Korkeala
>
>         _______________________________________________
>
>         java-devel mailing list -- [e-mail]
>
>         To unsubscribe send an email to [e-mail]
>
>         Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>
>         List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>
>         List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
>
>         Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>
>     _______________________________________________
>
>     java-devel mailing list -- [e-mail]
>
>     To unsubscribe send an email to [e-mail]
>
>     Fedora Code of Conduct:
>     https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>     <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
>
>     List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>     <https://fedoraproject.org/wiki/Mailing_list_guidelines>
>
>     List Archives:
>     https://lists.fedoraproject.org/archives/list/[e-mail]
>     <https://lists.fedoraproject.org/archives/list/[e-mail]>
>
>     Do not reply to spam on the list, report it:
>     https://pagure.io/fedora-infrastructure <https://pagure.io/fedora-infrastructure>

[Jerry James]

On Tue, Aug 2, 2022 at 8:05 AM Markku Korkeala  wrote:
> thanks all for the replies, I was running for the same issues with 3.2.0 version as well,
> good to see that return code 126 is fixable. Like I wrote in the opening message, I was
> able to add some debug messages and see that in the first case of Integer.MIN_VALUE return
> code, the exception returned from the process was:
> org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.
>
> (the test sends InvocationRequest and receives InvocationResponse, the response has
> the Exception and return code).
>
> But haven't got any deeper than that, what is the actual cause for the error.

I added some logging in DefaultInvoker.java (in method execute) to
print the exception when a CommandLineException is caught.  The two
failing tests are similar:

Exception: Failure processing stdout.
org.apache.maven.shared.utils.cli.CommandLineException: Failure
processing stdout.
    at org.apache.maven.shared.utils.cli.CommandLineUtils$2.call(CommandLineUtils.java:357)
    at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:185)
    at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:160)
    at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:141)
    at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:110)
    at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:186)
    at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:116)
    at org.apache.maven.shared.invoker.DefaultInvokerTest.testBuildShouldSucceed(DefaultInvokerTest.java:54)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:568)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:61)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
    at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
    at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
    at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
    at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
    at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
    at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:377)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:284)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:248)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:167)
    at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456)
    at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169)
    at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581)
Caused by: java.nio.BufferOverflowException
    at java.base/java.nio.Buffer.nextPutIndex(Buffer.java:722)
    at java.base/java.nio.HeapByteBuffer.put(HeapByteBuffer.java:209)
    at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encodeString(AbstractStreamEncoder.java:127)
    at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encodeStringData(AbstractStreamEncoder.java:171)
    at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encode(AbstractStreamEncoder.java:157)
    at org.apache.maven.surefire.booter.spi.EventChannelEncoder.encodeMessage(EventChannelEncoder.java:398)
    at org.apache.maven.surefire.booter.spi.EventChannelEncoder.setOutErr(EventChannelEncoder.java:188)
    at org.apache.maven.surefire.booter.spi.EventChannelEncoder.testOutput(EventChannelEncoder.java:183)
    at org.apache.maven.surefire.api.booter.ForkingRunListener.writeTestOutput(ForkingRunListener.java:113)
    at org.apache.maven.surefire.api.booter.ForkingRunListener.writeTestOutput(ForkingRunListener.java:44)
    at org.apache.maven.surefire.common.junit4.JUnit4RunListener.writeTestOutput(JUnit4RunListener.java:235)
    at org.apache.maven.surefire.api.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:138)
    at org.apache.maven.shared.invoker.PrintStreamHandler.consumeLine(PrintStreamHandler.java:76)
    at org.apache.maven.shared.utils.cli.StreamPumper.consumeLine(StreamPumper.java:158)
    at org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:88)

We have version 3.0.0-M6 of surefire in Rawhide, which has this bug:
https://issues.apache.org/jira/browse/SUREFIRE-2056.  It looks like
maven-invoker has run afoul of that bug.

[Markku Korkeala]

Hi,

thanks! So I guess for now I'll disable the two failing tests out and when the
maven-surefire is upgraded in Fedora I'll try to enable the tests again.

Thanks everyone!

Best regards,
Markku Korkeala

On 8/3/22 00:40, Jerry James wrote:
> On Tue, Aug 2, 2022 at 8:05 AM Markku Korkeala  wrote:
> > thanks all for the replies, I was running for the same issues with 3.2.0 version as well,
> > good to see that return code 126 is fixable. Like I wrote in the opening message, I was
> > able to add some debug messages and see that in the first case of Integer.MIN_VALUE return
> > code, the exception returned from the process was:
> > org.apache.maven.shared.utils.cli.CommandLineException:  Failure processing stdout.
> >
> > (the test sends InvocationRequest and receives InvocationResponse, the response has
> > the Exception and return code).
> >
> > But haven't got any deeper than that, what is the actual cause for the error.
>
> I added some logging in DefaultInvoker.java (in method execute) to
> print the exception when a CommandLineException is caught.  The two
> failing tests are similar:
>
> Exception: Failure processing stdout.
> org.apache.maven.shared.utils.cli.CommandLineException: Failure
> processing stdout.
>     at org.apache.maven.shared.utils.cli.CommandLineUtils$2.call(CommandLineUtils.java:357)
>     at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:185)
>     at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:160)
>     at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:141)
>     at org.apache.maven.shared.utils.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:110)
>     at org.apache.maven.shared.invoker.DefaultInvoker.executeCommandLine(DefaultInvoker.java:186)
>     at org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:116)
>     at org.apache.maven.shared.invoker.DefaultInvokerTest.testBuildShouldSucceed(DefaultInvokerTest.java:54)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>     at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
>     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:61)
>     at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>     at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
>     at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
>     at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
>     at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
>     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
>     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
>     at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
>     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
>     at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
>     at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
>     at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:377)
>     at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:284)
>     at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:248)
>     at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:167)
>     at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456)
>     at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169)
>     at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595)
>     at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581)
> Caused by: java.nio.BufferOverflowException
>     at java.base/java.nio.Buffer.nextPutIndex(Buffer.java:722)
>     at java.base/java.nio.HeapByteBuffer.put(HeapByteBuffer.java:209)
>     at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encodeString(AbstractStreamEncoder.java:127)
>     at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encodeStringData(AbstractStreamEncoder.java:171)
>     at org.apache.maven.surefire.api.stream.AbstractStreamEncoder.encode(AbstractStreamEncoder.java:157)
>     at org.apache.maven.surefire.booter.spi.EventChannelEncoder.encodeMessage(EventChannelEncoder.java:398)
>     at org.apache.maven.surefire.booter.spi.EventChannelEncoder.setOutErr(EventChannelEncoder.java:188)
>     at org.apache.maven.surefire.booter.spi.EventChannelEncoder.testOutput(EventChannelEncoder.java:183)
>     at org.apache.maven.surefire.api.booter.ForkingRunListener.writeTestOutput(ForkingRunListener.java:113)
>     at org.apache.maven.surefire.api.booter.ForkingRunListener.writeTestOutput(ForkingRunListener.java:44)
>     at org.apache.maven.surefire.common.junit4.JUnit4RunListener.writeTestOutput(JUnit4RunListener.java:235)
>     at org.apache.maven.surefire.api.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:138)
>     at org.apache.maven.shared.invoker.PrintStreamHandler.consumeLine(PrintStreamHandler.java:76)
>     at org.apache.maven.shared.utils.cli.StreamPumper.consumeLine(StreamPumper.java:158)
>     at org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:88)
>
> We have version 3.0.0-M6 of surefire in Rawhide, which has this bug:
> https://issues.apache.org/jira/browse/SUREFIRE-2056.  It looks like
> maven-invoker has run afoul of that bug.