incubator-stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Sebor <se...@roguewave.com>
Subject Re: failed examples reported as passing with MSVC or vice versa
Date Wed, 20 Dec 2006 06:52:46 GMT
Andrew Black wrote:

[...]
> My reading of this message is that the runall.wsf script failed to 
> complete a file system command.  Unfortunately, I am having difficulties 
> determining where the failure occurred, as the line number is 
> meaningless within the context of a text editor.  I tend to suspect that 
> this translates to line 118 of the runall.wsf script.  A potential 
> contributing cause is the permissions of the build directory used by the 
> nightly testing system.

Permissions on Windows? That's something new! Could you look
into this theory some more when you have a spare moment? We
need to get those builds working at some point in the near
future.

Thanks!
Martin

> 
> --Andrew Black
> 
> Martin Sebor wrote:
> 
>> While going through our MSVC 8.0 jumbled up log I came across
>> what looks like incorrect behavior of either the exec utility
>> or the Windows infrastructure. What seems to be happening is
>> that while exec reports some examples as passing the rest of
>> the infrastructure actually says they failed. Below are lines
>> from the log relevant to the accumulate.exe example.
>>
>> Andrew and/or Farid, could you guys look into it to see which
>> part of the infrastructure is broken?
>>
>> Thanks
>> Martin
>>
>> 422>Performing Custom Build Step
>> 422>running accumulate.exe
>> 422>NAME                      STATUS WARN ASSERTS FAILED PERCNT    
>> USER     SYS    REAL
>> 422>accumulate.exe                 0    0           0.330
>> 422>example output differs from the expected
>> 422>example failed! Exit code 0
>> 422>


Mime
View raw message