[Adium-devl] Assertion failures

[Colin Barrett]

Hm.

It would be nice for those asserts to not show up in the test output,  
but I'm less worried.

Thanks,
-Colin

On Jul 28, 2008, at 3:05 PM, Evan Schoenberg wrote:

> 2008-07-28 15:45:27.521 otest[17604:80f] *** Assertion failure in - 
> [AIWiredData initWithBytes:length:], /Users/adium/adium-slave/ 
> trunk-10.5-x86/build/Frameworks/AIUtilities Framework/Source/ 
> AIWiredData.m:76
> Test Case '-[TestWiredData testAutoreleasedDataWithNULLBytes]'  
> passed (0.005 seconds).
>
>
> 2008-07-28 15:45:27.528 otest[17604:80f] *** Assertion failure in - 
> [AIWiredData assertValidRange:], /Users/adium/adium-slave/trunk-10.5- 
> x86/build/Frameworks/AIUtilities Framework/Source/AIWiredData.m:109
> Test Case '-[TestWiredData testGetBytesInvalidRange]' passed (0.004  
> seconds).
>
> These are tests that the assertion is, in fact, being thrown in  
> situations that it should - they're by design.
>
> -Evan
>
> On Jul 28, 2008, at 5:44 PM, Colin Barrett wrote:
>
>> Looking at the test output from buildbot[1], I'm seeing a number of
>> assertion failures. Are these by design? Either way, we should not
>> have assertion failures in passing test output, IMO.
>>
>> Thoughts?
>> -Colin
>>
>> [1]: http://duck.adiumx.com:8080/builders/trunk-10.5-x86/builds/1072/steps/test/logs/stdio
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20080729/d74f2db4/attachment-0001.html>