Skip to content

Treat JUnit errors as failures to increase visibility #9698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion app/build.xml
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@
<fileset dir="test" includes="**/*.pac" />
</copy>

<junit printsummary="yes" dir="${work.dir}" fork="true">
<junit printsummary="yes" dir="${work.dir}" fork="true" showoutput="yes" failureproperty="test.failed">
<jvmarg value="-Djava.library.path=${java.additional.library.path}"/>
<jvmarg value="-DWORK_DIR=."/>
<jvmarg value="-ea"/>
Expand All @@ -131,6 +131,7 @@
</batchtest>
</junit>

<fail if="test.failed"/>
</target>

<target name="build" depends="compile" description="Build PDE">
Expand Down