Hi Dan,

It looks like while your tests are executed and passed, the java processes
executing those tests did not exit properly.
- Could you try execute the command manually and see if there's any useful
outputs? You can find the commands by searching "Command was" in the maven
logs.
- Quick question: which PR are you working on? By any chance you called
`System.exit()` in your codes?

Thank you~

Xintong Song



On Thu, Oct 22, 2020 at 5:59 AM Dan Hill <quietgol...@gmail.com> wrote:

> Sure, here's a link
> <https://drive.google.com/file/d/13Q7h77zG-2vp7gJOke8QAzLtKLKIPuTf/view?usp=sharing>
>  to
> the output.  I think for this one I used either:
> - `mvn package -e -X -DfailIfNoTests=false`
> - or added a `clean` before package.
>
> On Wed, Oct 21, 2020 at 2:24 AM Xintong Song <tonysong...@gmail.com>
> wrote:
>
>> Would you be able to share the complete maven logs and the command? And
>> what is the maven version?
>>
>> Thank you~
>>
>> Xintong Song
>>
>>
>>
>> On Wed, Oct 21, 2020 at 1:37 AM Dan Hill <quietgol...@gmail.com> wrote:
>>
>>> Hi Xintong!
>>>
>>> No changes.  I tried -X and no additional log information is logged.
>>> -DfailIfNoTests=false does not help.  `-DskipTests` works fine.  I'm going
>>> to go ahead and create a PR and see if it fails.
>>>
>>> Thanks!
>>> - Dan
>>>
>>> On Tue, Oct 20, 2020 at 8:22 AM Xintong Song <tonysong...@gmail.com>
>>> wrote:
>>>
>>>> Hi Dan,
>>>>
>>>> The 'mvn package' command automatically includes 'mvn verify', which
>>>> triggers the test cases. You can skip the tests with 'mvn package
>>>> -DskipTests'. You can rely on the ci-tests running on Azure Pipeline,
>>>> either in your own workspace or in the PR.
>>>>
>>>> If it is intended to execute the tests locally, you can try the
>>>> following actions. I'm not sure whether that helps though.
>>>> - Try to add '-DfailIfNoTests=false' to your maven command.
>>>> - Execute the maven command with '-X' to print all the debug logs.
>>>>
>>>> Thank you~
>>>>
>>>> Xintong Song
>>>>
>>>>
>>>>
>>>> On Tue, Oct 20, 2020 at 3:48 PM Dan Hill <quietgol...@gmail.com> wrote:
>>>>
>>>>> I forked Flink to work on a PR.  When I run `mvn clean package` from a
>>>>> clean branch, Maven says the runtime tests failed but the logs do not
>>>>> appear to have details on the failure.  Do I have to do anything to run
>>>>> these?
>>>>>
>>>>>
>>>>>
>>>>> ...
>>>>>
>>>>> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 2.24 s - in org.apache.flink.runtime.taskexecutor.
>>>>> BackPressureSampleServiceTest
>>>>>
>>>>> [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 1.872 s - in org.apache.flink.runtime.taskexecutor.partition.
>>>>> PartitionTableTest
>>>>>
>>>>> [DEBUG] Forking command line: /bin/sh -c cd
>>>>> /Users/quietgolfer/code/dan-flink/flink/flink-runtime &&
>>>>> /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/bin/java
>>>>> -Xms256m -Xmx2048m -Dmvn.forkNumber=9 -XX:+UseG1GC -jar
>>>>> /Users/quietgolfer/code/dan-flink/flink/flink-runtime/target/surefire/surefirebooter3345042301183877750.jar
>>>>> /Users/quietgolfer/code/dan-flink/flink/flink-runtime/target/surefire
>>>>> 2020-10-19T23-54-59_239-jvmRun9 surefire7884081050263655575tmp
>>>>> surefire_7142433009722615751420tmp
>>>>>
>>>>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 2 s - in org.apache.flink.runtime.taskexecutor.slot.
>>>>> TaskSlotTest
>>>>>
>>>>> [INFO] Running org.apache.flink.runtime.taskexecutor.
>>>>> NettyShuffleEnvironmentConfigurationTest
>>>>>
>>>>> [INFO] Running org.apache.flink.runtime.taskexecutor.slot.
>>>>> TaskSlotTableImplTest
>>>>>
>>>>> [INFO] Running org.apache.flink.runtime.taskexecutor.
>>>>> TaskExecutorToResourceManagerConnectionTest
>>>>>
>>>>> [INFO] Running org.apache.flink.runtime.taskexecutor.slot.
>>>>> TimerServiceTest
>>>>>
>>>>> [INFO] Running akka.actor.RobustActorSystemTest
>>>>>
>>>>> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 2.077 s - in org.apache.flink.runtime.taskexecutor.
>>>>> NettyShuffleEnvironmentConfigurationTest
>>>>>
>>>>> [INFO] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 3.009 s - in org.apache.flink.runtime.taskexecutor.slot.
>>>>> TaskSlotTableImplTest
>>>>>
>>>>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 4.088 s - in org.apache.flink.runtime.taskexecutor.slot.
>>>>> TimerServiceTest
>>>>>
>>>>> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 4.986 s - in org.apache.flink.runtime.taskexecutor.
>>>>> TaskExecutorToResourceManagerConnectionTest
>>>>>
>>>>> [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 5.146 s - in akka.actor.RobustActorSystemTest
>>>>>
>>>>> [INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 11.309 s - in org.apache.flink.runtime.taskexecutor.
>>>>> TaskExecutorTest
>>>>>
>>>>> [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time
>>>>> elapsed: 11.068 s - in org.apache.flink.runtime.taskexecutor.
>>>>> TaskManagerRunnerTest
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] Results:
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [WARNING] Tests run: 4813, Failures: 0, Errors: 0, Skipped: 50
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> [INFO] Reactor Summary for Flink : 1.12-SNAPSHOT:
>>>>>
>>>>> [INFO]
>>>>>
>>>>> [INFO] Flink : Tools : Force Shading ...................... SUCCESS [
>>>>> 1.736 s]
>>>>>
>>>>> [INFO] Flink : ............................................ SUCCESS [
>>>>> 15.601 s]
>>>>>
>>>>> [INFO] Flink : Annotations ................................ SUCCESS [
>>>>> 14.502 s]
>>>>>
>>>>> [INFO] Flink : Test utils : ............................... SUCCESS [
>>>>> 12.505 s]
>>>>>
>>>>> [INFO] Flink : Test utils : Junit ......................... SUCCESS [
>>>>> 15.152 s]
>>>>>
>>>>> [INFO] Flink : Metrics : .................................. SUCCESS [
>>>>> 12.443 s]
>>>>>
>>>>> [INFO] Flink : Metrics : Core ............................. SUCCESS [
>>>>> 14.250 s]
>>>>>
>>>>> [INFO] Flink : Core ....................................... SUCCESS
>>>>> [01:23 min]
>>>>>
>>>>> [INFO] Flink : Java ....................................... SUCCESS [
>>>>> 43.248 s]
>>>>>
>>>>> [INFO] Flink : Queryable state : .......................... SUCCESS [
>>>>> 10.139 s]
>>>>>
>>>>> [INFO] Flink : Queryable state : Client Java .............. SUCCESS [
>>>>> 16.857 s]
>>>>>
>>>>> [INFO] Flink : FileSystems : .............................. SUCCESS [
>>>>> 13.203 s]
>>>>>
>>>>> [INFO] Flink : FileSystems : Hadoop FS .................... SUCCESS [
>>>>> 25.514 s]
>>>>>
>>>>> [INFO] Flink : Runtime .................................... FAILURE
>>>>> [11:05 min]
>>>>>
>>>>> [INFO] Flink : Scala ...................................... SKIPPED
>>>>>
>>>>

Reply via email to