• Gorge Jingale (10/10) Jul 25 2016 dustmite doesn't seem to work correctly. I always get
• Rainer Schuetze (4/14) Jul 26 2016 It seems Visual D missed the transition of error messages being printed
• Gorge Jingale (12/37) Jul 26 2016 ?
• Rainer Schuetze (3/15) Jul 27 2016 I meant the output window that displays the compilation error (before

Gorge Jingale <Frifj mail.com> writes:

dustmite doesn't seem to work correctly. I always get

"object.Exception ..\dustmite.d(271): Initial test fails"

Regardless of what I do. I think this is a problem in the design 
of VD using dustmite. Could you allow for setting options for 
dustmite. First the test string.. It might not always be 
"Internal error". Second is the error code. Sometimes utilities 
spit out the opposite of what dustmite wants.

Even if I create a new project without any modifications, The VD 
dustmite fails. If I add a syntax error, dustmite fails, If I add 
a runtime error, dustmite fails. Dustmite allways fails ;/

Rainer Schuetze <r.sagitario gmx.de> writes:

On 26.07.2016 01:05, Gorge Jingale wrote:
 dustmite doesn't seem to work correctly. I always get

 "object.Exception ..\dustmite.d(271): Initial test fails"

 Regardless of what I do. I think this is a problem in the design of VD
 using dustmite. Could you allow for setting options for dustmite. First
 the test string.. It might not always be "Internal error". Second is the
 error code. Sometimes utilities spit out the opposite of what dustmite
 wants.

You can set the test string by selecting it in the output window.

 Even if I create a new project without any modifications, The VD
 dustmite fails. If I add a syntax error, dustmite fails, If I add a
 runtime error, dustmite fails. Dustmite allways fails ;/

It seems Visual D missed the transition of error messages being printed 
to stderr instead of stdout. I'll fix that...

Gorge Jingale <Frifj mail.com> writes:

On Tuesday, 26 July 2016 at 07:43:36 UTC, Rainer Schuetze wrote:
 On 26.07.2016 01:05, Gorge Jingale wrote:
 dustmite doesn't seem to work correctly. I always get

 "object.Exception ..\dustmite.d(271): Initial test fails"

 Regardless of what I do. I think this is a problem in the 
 design of VD
 using dustmite. Could you allow for setting options for 
 dustmite. First
 the test string.. It might not always be "Internal error". 
 Second is the
 error code. Sometimes utilities spit out the opposite of what 
 dustmite
 wants.

 You can set the test string by selecting it in the output 
 window.

?

The output window is:

created clean copy of the project in A.dustmite
Spawned dustmite, check new console window for output...

And the console is just the output of dustmite's results(nothing 
to change there).

When I run dustmite from VD, I get a dialog box "Do I want to 
reduce using dustmite with internal error", so after that point, 
it's too late to change.

So, I guess we are talking about two different output windows.

 Even if I create a new project without any modifications, The 
 VD
 dustmite fails. If I add a syntax error, dustmite fails, If I 
 add a
 runtime error, dustmite fails. Dustmite allways fails ;/

 It seems Visual D missed the transition of error messages being 
 printed to stderr instead of stdout. I'll fix that...

Thanks.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 26.07.2016 21:16, Gorge Jingale wrote:
 You can set the test string by selecting it in the output window.

 ?

 The output window is:

 created clean copy of the project in A.dustmite
 Spawned dustmite, check new console window for output...

 And the console is just the output of dustmite's results(nothing to
 change there).

 When I run dustmite from VD, I get a dialog box "Do I want to reduce
 using dustmite with internal error", so after that point, it's too late
 to change.

 So, I guess we are talking about two different output windows.

I meant the output window that displays the compilation error (before 
you invoke dustmite).