[
https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833922#comment-16833922
]
Tibor Digana commented on SUREFIRE-1623:
----------------------------------------
[~ChrisGWarp]
Thx Chris, the execution time is too long against my system (AMD Athlon 64
3800+ II Core) but it is not what I understand by hanging. Because the build
has finished.
Few weeks ago on our Mailing list one user said that he had significantly slow
GC and he said that it was a problem with the system because he configured a
swap file. I understood him that JVM used swap for perm-generation but he did
not explain details.
Pls check your system too, {{Xmx}} and possibly use {{jconsole}}.
There is dump file(s) in the directory {{target/surefire-reports}}, pls go
there and try to find them. Perhaps they would tell us more what's going on
inside.
> TempWmicBatchFile.bat is left in project dirs after surefire tests are run
> --------------------------------------------------------------------------
>
> Key: SUREFIRE-1623
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1623
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 3.0.0-M3
> Reporter: Chris Graham
> Assignee: Tibor Digana
> Priority: Blocker
> Attachments: reproduce-surefire-issue master.zip
>
>
> WINDOWS ONLY:
> When the WMIC command it run to obtain the process start time, the current
> implementation leaves behind a batch file, TempWmicBatchFile.bat, which is
> zero bytes long.
> This file needs to be removed post execution.
> Leaving it behind will interfere with the release plugin as a scm status call
> will fail with files needing to be added. Simply ignoring the file is a very
> sloppy approach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
