• Alex (11/11) Apr 28 2019 Suspicious file found: D:\.dustmite\build.dustmite.bat
• Seb (8/19) Apr 29 2019 You need to run DustMite in a project that reproduces the

Alex <AJ gmail.com> writes:

Suspicious file found: D:\.dustmite\build.dustmite.bat
You should use a clean copy of the source tree.
If it was your intention to include this file in the file-set to 
be reduced,
re-run dustmite with the --force option.

adding force, it then asks me to overwrite dir, then I get

D:\.dustmite\Repos\S\S: The process cannot access the file 
because it is being used by another process.

dustmite --strip-comments --no-redirect --split *.bat:lines 
D:\.dustmite "build.dustmite.bat 2>&1 | find \"Internal error\""

Ultimatly dustmite does nothing.

Seb <seb wilzba.ch> writes:

On Sunday, 28 April 2019 at 22:02:32 UTC, Alex wrote:
 Suspicious file found: D:\.dustmite\build.dustmite.bat
 You should use a clean copy of the source tree.
 If it was your intention to include this file in the file-set 
 to be reduced,
 re-run dustmite with the --force option.

 adding force, it then asks me to overwrite dir, then I get

 D:\.dustmite\Repos\S\S: The process cannot access the file 
 because it is being used by another process.

 dustmite --strip-comments --no-redirect --split *.bat:lines 
 D:\.dustmite "build.dustmite.bat 2>&1 | find \"Internal error\""

 Ultimatly dustmite does nothing.

You need to run DustMite in a project that reproduces the 
error/behavior you want to reduce minimally. That's what the 
first warning is about.
I typically copy over the D file(s) required to reproduce the 
behavior in a fresh folder and run DustMite there.

For more info, please see its documentation:

https://github.com/CyberShadow/DustMite/wiki