Hi Colm,

I saw this failure - but the latest build is stable. There was also
aync stuff changes [1].
The Netty upgrade can be easily reverted to monitor the actual failure reason.

1. https://github.com/apache/cxf/commit/3921fc29c265addfa36d0b4260903eef96ac1e25

On 4/2/20, Colm O hEigeartaigh <[email protected]> wrote:
> Hi Alexey,
>
> It looks like this upgrade is causing a test failure:
>
> - [ERROR]
> testCallAsync(org.apache.cxf.transport.http.netty.client.integration.NettyClientTest)
>  Time elapsed: 1.186 s  <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.cxf.transport.http.netty.client.integration.NettyClientTest.testCallAsync(NettyClientTest.java:129)
>
> Colm.
>
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Mon, Mar 30, 2020 at 11:35 AM
> Subject: [cxf] 01/03: Upgrade to Netty 4.1.48.Final
> To: [email protected] <[email protected]>
>
>
> This is an automated email from the ASF dual-hosted git repository.
>
> buhhunyx pushed a commit to branch master
> in repository https://gitbox.apache.org/repos/asf/cxf.git
>
> commit 2cff3ce96abb43a5171d047984a47a37c1c2ea68
> Author: Alexey Markevich <[email protected]>
> AuthorDate: Mon Mar 30 11:36:15 2020 +0300
>
>     Upgrade to Netty 4.1.48.Final
> ---
>  parent/pom.xml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/parent/pom.xml b/parent/pom.xml
> index 04b8171..fb30a9a 100644
> --- a/parent/pom.xml
> +++ b/parent/pom.xml
> @@ -172,7 +172,7 @@
>          <cxf.msv.version>2013.6.1</cxf.msv.version>
>          <cxf.neethi.version>3.1.1</cxf.neethi.version>
>          <cxf.netty.version.range>[4,5)</cxf.netty.version.range>
> -        <cxf.netty.version>4.1.45.Final</cxf.netty.version>
> +        <cxf.netty.version>4.1.48.Final</cxf.netty.version>
>          <cxf.oauth.version>20100527</cxf.oauth.version>
>          <cxf.olingo.version>2.0.11</cxf.olingo.version>
>          <cxf.openjpa.version>3.1.0</cxf.openjpa.version>
>

Reply via email to