[
https://issues.apache.org/jira/browse/SUREFIRE-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075072#comment-17075072
]
Tibor Digana commented on SUREFIRE-1339:
----------------------------------------
[~michael-o]
I have checked the integration test Surefire772BothReportsIT, as well as the
outcome of running the test and the requirement in the issue SUREFIRE-772. IMO
you have touched the behavior of {{java.io.File.isFile}} and wrongly written IT.
The purpose of this IT is to skip generating the HTML report which is controled
by *<skipSurefireReport>true</skipSurefireReport>*. The issue SUREFIRE-772
says that the next potentional report must not be generated. I do not
understand why the test has this assertion statement:
{code:java}
assertTrue( "Expecting failsafe report file", siteFile.isFile() );
{code}
and why it is not this statement:
assertFalse( "Not expecting failsafe report file", siteFile.exists() );
It would be nice to have an INFO log in the plugin saying that the report is
forcibly skipped. Currently the logs don't express this situation:
{noformat}
[INFO] --- maven-surefire-report-plugin:3.0.0-SNAPSHOT:report-only
(default-cli) @ junit-twoTestCases ---
[WARNING] Unable to locate Test Source XRef to link to - DISABLED
{noformat}
> Forked JVM hangs in FreeBSD when reuseForks=true
> ------------------------------------------------
>
> Key: SUREFIRE-1339
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1339
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Environment: FreeBSD
> Reporter: Tibor Digana
> Assignee: Tibor Digana
> Priority: Major
>
> The event RUN_CLASS is not received by forked JVM after started.
> The events are received as soon as the JVM exited.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
