https://bz.apache.org/bugzilla/show_bug.cgi?id=66411
Bug ID: 66411
Summary: JUnitLauncher task fails on forked test timeout even
if haltOnFailure is false
Product: Ant
Version: 1.10.12
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Optional Tasks
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
We have been migrating from junit 4 (junit ant task) to junit 5
(junitlauncher).
Where we previously had:
<junit fork="yes" haltonfailure="${junit.haltonfailure}" ...
we have:
<junitlauncher haltonfailure="${junit.haltonfailure}" ...>
<fork timeout="${junit.timeout}"> ...
The fact that this fork works per test suite and not per test was a suprise but
not a deal breaker. However we are executing hundreds of tests in forked JVMs
(Loop in JUnitLauncherTask.java:96) and whenever one fails whole builds goes
belly up insantly.
It seems that the case of exitCode being equal to
Constants.FORK_EXIT_CODE_TIMED_OUT should be threated the same way as when it
equals Constants.FORK_EXIT_CODE_TESTS_FAILED in JUnitLauncherTask.java:301/332.
What are your thoughts?
--
You are receiving this mail because:
You are the assignee for the bug.
