@dockerzhang <[email protected]>, @Aloys Zhang <[email protected]> and
all:

I personally agree to roll back the version, make improvements to the unit
test case, and then reissue the version.

No problems were found by adopting @Aloys Zhang <[email protected]>'s
command "mvn clean package -DskipTests" today. I suspect that the problem
reported by @Aloys Zhang <[email protected]> was caused by its
compilation environment, but another new problem was found:

First use “mvn clean package install”, then “mvn test”, the error is
reported in “mvn test”, and it can be reproduced[1][2].

At the same time, it is found that there are problems in some unit tests.
There are many errors, but why there are no error reports?

Thanks!

1. the error snapshot:
[image: 企业微信截图_16441204276786.png]

2. the reports:










*-------------------------------------------------------------------------------Test
set:
org.apache.inlong.sort.singletenant.flink.kafka.RowToJsonKafkaSinkTest-------------------------------------------------------------------------------Tests
run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 123.229 s <<<
FAILURE! - in
org.apache.inlong.sort.singletenant.flink.kafka.RowToJsonKafkaSinkTesttestKafkaSink(org.apache.inlong.sort.singletenant.flink.kafka.RowToJsonKafkaSinkTest)
 Time elapsed: 122.909 s  <<<
ERROR!java.util.concurrent.ExecutionException:
org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a
node assignment.Caused by: org.apache.kafka.common.errors.TimeoutException:
Timed out waiting for a node
assignment.testKafkaSink(org.apache.inlong.sort.singletenant.flink.kafka.RowToJsonKafkaSinkTest)
 Time elapsed: 122.909 s  <<< ERROR!java.lang.NullPointerException*










*-------------------------------------------------------------------------------Test
set:
org.apache.inlong.sort.singletenant.flink.kafka.RowToStringKafkaSinkTest-------------------------------------------------------------------------------Tests
run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 3.055 s <<<
FAILURE! - in
org.apache.inlong.sort.singletenant.flink.kafka.RowToStringKafkaSinkTesttestKafkaSink(org.apache.inlong.sort.singletenant.flink.kafka.RowToStringKafkaSinkTest)
 Time elapsed: 3.051 s  <<< ERROR!org.apache.kafka.common.KafkaException:
Socket server failed to bind to 0.0.0.0:9092 <http://0.0.0.0:9092>: Address
already in use: bind.Caused by: java.net.BindException: Address already in
use:
bindtestKafkaSink(org.apache.inlong.sort.singletenant.flink.kafka.RowToStringKafkaSinkTest)
 Time elapsed: 3.051 s  <<< ERROR!java.lang.NullPointerException*


Goson zhang <[email protected]> 于2022年2月5日周六 23:18写道:

> @dockerzhang <[email protected]>, or anyone else, when you verify
> it[1], have you reproduced the issue that @Aloys Zhang
> <[email protected]> was talking about?
>
> I double-checked this problem: I deleted the local repository,
> re-extracted the release package from the release email, compiled it
> multiple times with the commands "mvn compile", "mvn clean package" and
> "mvn clean package install", all successful
>
> I think we need to find out the cause of this problem first, or if we do
> release it again, it is very likely that we will encounter the same problem
> again.
>
> Please tell me about your situation, thanks!!
>
> 1. https://inlong.apache.org/development/how-to-verify
>
>
>
> Aloys Zhang <[email protected]> 于2022年2月5日周六 20:15写道:
>
>> @[email protected] <[email protected]>  you can try `mvn clean
>> package -DskipTests`
>>
>> Goson zhang <[email protected]> 于2022年2月5日周六 19:56写道:
>>
>>> @Aloys Zhang <[email protected]>, How did you discover this problem?
>>>
>>> It feels a bit strange and I want to confirm the problem, I started
>>> using "mvn compile", the whole compilation has been completed.
>>>
>>> Thanks!
>>>
>>> Aloys Zhang <[email protected]> 于2022年2月5日周六 19:15写道:
>>>
>>>> -1.
>>>>
>>>> @docker Thanks for your work on releasing, but I'm afraid that I  have
>>>> to vote -1 since the release branch has a compilation failure caused by
>>>> incompatible dependencies of kafka-client.
>>>> [image: image.png]
>>>>
>>>> healchow <[email protected]> 于2022年2月5日周六 17:52写道:
>>>>
>>>>> +1.
>>>>> Checked: - Download links are valid. - Checksums and signatures. -
>>>>> LICENSE/NOTICE/DISCLAIMER files exist - No unexpected binary files - All
>>>>> source files have ASF headers - Can compile from source - All Tests Passed
>>>>> Thanks!
>>>>> On 2022/02/05 00:11 Zirui Peng<[email protected]> wrote:
>>>>> +1
>>>>> Checked - Download links are valid. - Checksums and signatures. -
>>>>> LICENSE/NOTICE/DISCLAIMER files exist - No unexpected binary files - All
>>>>> source files have ASF headers - Can compile from source - All Tests Passed
>>>>> Thanks! On 2022/02/02 14:56:17 dockerzhang wrote: > Hello Apache InLong
>>>>> PPMC and Community, > > This is a call for a vote to release Apache InLong
>>>>> version > 1.0.0-incubating-RC0. > > The tag to be voted on is
>>>>> 1.0.0-incubating-RC0: > >
>>>>> https://github.com/apache/incubator-inlong/tree/1.0.0-incubating-RC0
>>>>> > > The release tarball, signature, and checksums can be found at: > >
>>>>> https://dist.apache.org/repos/dist/dev/incubator/inlong/1.0.0-incubating-RC0/
>>>>> > > Maven artifacts are available in a staging repository at: > >
>>>>> https://repository.apache.org/content/repositories/orgapacheinlong-1068
>>>>> > > Artifacts were signed with the A4D4D578 key which can be found in: > >
>>>>> https://downloads.apache.org/incubator/inlong/KEYS > >
>>>>> 1.0.0-incubating includes ~ 124 bug fixes and improvements done > since
>>>>> last versions which can be found at: > >
>>>>> https://github.com/apache/incubator-inlong/blob/1.0.0-incubating-RC0/CHANGES.md
>>>>> > > Please download, verify, and test. > > The VOTE will remain open for 
>>>>> > > at
>>>>> least 72 hours. > > [ ] +1 Release this package as Apache InLong
>>>>> 1.0.0-incubating > [ ] +0 > [ ] -1 Do not release this package because... 
>>>>> >
>>>>> > To learn more about apache inlong, please see >
>>>>> http://inlong.apache.org/ > > Checklist for reference: > > [ ]
>>>>> Download links are valid. > [ ] Checksums and signatures. > [ ]
>>>>> LICENSE/NOTICE/DISCLAIMER files exist > [ ] No unexpected binary files > [
>>>>> ] All source files have ASF headers > [ ] Can compile from source > [ ] 
>>>>> All
>>>>> Tests Passed > > More detailed checklist please refer to: >
>>>>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>>>>> > > Thanks, > Your InLong Release Manager >
>>>>
>>>>

Reply via email to