[
http://jira.codehaus.org/browse/SUREFIRE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207461#action_207461
]
Kristian Rosenvold commented on SUREFIRE-593:
-
The bit about null.txt and TEST-org.junit.runner.Result.xml was probably
fixed in SUREFIRE-596, which is part of surefire 2.5 release.
I would suspect that the actual test failure is related to some locale setting
a file-system-type releated issue. Which file system is used?
If you were using junit 4.7+, please re-test with surefire 2.5 release and
provide updated results.
Tag surefire-2.5 creates null.txt as test report
Key: SUREFIRE-593
URL: http://jira.codehaus.org/browse/SUREFIRE-593
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.5
Environment: Windows XP Pro, maven 2.2.1
Reporter: Kiril Raychev
Attachments: settings.xml
When executing 'mvn install' on the tags/surefire-2.5 release (r897179) I get
one failing test:
Running org.apache.maven.surefire.its.UmlautDirIT
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.219 sec
FAILURE!
When executing 'mvn install -Dmaven.test.skip=true' the build succeeds, but
when it is used on other project, the only output to target/surefire-reports
are null.txt and TEST-org.junit.runner.Result.xml, which contain report of
the last test class run.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira