maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Graham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-1623) TempWmicBatchFile.bat is left in project dirs after surefire tests are run
Date Sun, 05 May 2019 11:51:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833348#comment-16833348
] 

Chris Graham commented on SUREFIRE-1623:
----------------------------------------

My intent in the above, perhaps would have been clearer if instead of 'paranoid', I wrote
'to program defensively', ie, only remove the file if the file was present before the execution.
I have lots of issues getting 1.8 installed in this VM, so I've had to go back to 1.8.0_40
and then install newer versions after that (an initial install of 1.8.0_181 or 191 did not
work).
Simply running 'mvn clean install' on surefire itself produces the WMIC files left behind,
and the next build fails on a rat check.
I will try to get to a point where I can build surefire under 32 bit XP and then see if I
can drill down deeper into the code to see what is triggering the issue.


> 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)

Mime
View raw message