JUnit5 generates a negative execution time for test case unexpectedly

[ZzhengSyna]

This should be a rare scenario, I haven't seen it before.
Basically I was running a JUnit5 test on an android S device, using ./gradlew connectedDebugAndroid. Inside my test project, there are 9 cases, each is run with @RepeatedTest(9), so if everything goes well, there should be 81 cases in total.

Now I ran this suite for multiple times, and met twice of the below issue:
During my test, something goes wrong(should be a bug in the android system), from the console log of the android device, I can see the android system crashed with a Kernel panic. So the test suite was terminated, somehow, an invalid test duration was generated: time="-1.73649439603E9".

From the generated xml test report, I can see something like this:

<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 1 of 9" time="109.09"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 2 of 9" time="107.962"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 3 of 9" time="107.832"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 4 of 9" time="108.991"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 5 of 9" time="107.835"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 6 of 9" time="107.884"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 7 of 9" time="107.725"/>
<testcase classname="com.xxx.MainTest" name="testFrameDropTunnelModeEnabled: repetition 8 of 9" time="-1.73649439603E9"/>

<testcase classname="com.xxx.MainTest" name="testVerticalTunnelModeEnabled: repetition 1 of 9" time="21.424"/>
<testcase classname="com.xxx.MainTest" name="testVerticalTunnelModeEnabled: repetition 2 of 9" time="20.345"/>
<testcase classname="com.xxx.MainTest" name="testVerticalTunnelModeEnabled: repetition 3 of 9" time="-1.736494169664E9"/>

Note the two special execution time: time="-1.73649439603E9" and time="-1.736494169664E9".
This is unexpected, I think JUnit should set them as failure or error?

The plugins I'm using:

// In project level build.grale
classpath 'com.android.tools.build:gradle:3.6.3'
classpath 'de.mannodermaus.gradle.plugins:android-junit5:1.6.0.0'

// In app level build.gradle
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
testInstrumentationRunnerArgument "runnerBuilder", "de.mannodermaus.junit5.AndroidJUnit5Builder"

...

androidTestRuntimeOnly "de.mannodermaus.junit5:android-test-runner:1.2.0"

If additional info is required, please kindly let me know.

[ZzhengSyna]

Find a similar xml result:

<testcase classname="com.xyz.MainTest" name="testDolbyVisionTunnelModeEnabled: repetition 12 of 90" time="20.314"/>
<testcase classname="com.xyz.MainTest" name="testDolbyVisionTunnelModeEnabled: repetition 13 of 90" time="22.07"/>
<testcase classname="com.xyz.MainTest" name="testDolbyVisionTunnelModeEnabled: repetition 14 of 90" time="20.162"/>
<testcase classname="com.xyz.MainTest" name="testDolbyVisionTunnelModeEnabled: repetition 15 of 90" time="-1.736740711497E9"/>
</testsuite>

[ZzhengSyna]

Found again:

<testcase classname="com.xyz.MainTest" name="testVerticalTunnelModeEnabled: repetition 28 of 90" time="20.22"/>
<testcase classname="com.xyz.MainTest" name="testVerticalTunnelModeEnabled: repetition 29 of 90" time="20.2"/>
<testcase classname="com.xyz.MainTest" name="testVerticalTunnelModeEnabled: repetition 30 of 90" time="20.195"/>
<testcase classname="com.xyz.MainTest" name="testVerticalTunnelModeEnabled: repetition 31 of 90" time="20.194"/>
<testcase classname="com.xyz.MainTest" name="testVerticalTunnelModeEnabled: repetition 32 of 90" time="-1.736757829469E9"/>
</testsuite>

[mannodermaus]

I have seen negative execution times in the past as well. Judging from your build environment, I'd first need to rule out any fixes in the meantime, however. You are running version 3.x of the Android Gradle plugin and 1.6.x of this plugin for JUnit 5, both of which are seriously outdated. Is there any particular reason you cannot go to a higher version? I don't intend to fix anything on a plugin that's five years old.

[ZzhengSyna]

Okay, I will try to update the versions later to see if the issue could be fixed.
Are there any known fixes in the later versions?
Thanks