[racket-dev] Contract Errors in the Test Suite

FYI, I've submitted a bug to the bug tracker detailing this problem.

Will

On Sep 11, 2010, at 5:04 PM, Will M. Farr wrote:

> I've finished the testing of configure options.  It seems to be the places library.  Running with or without optimization options, the --enable-places flag to configure generates a racket that fails the contract tests in the way I described in my original email.  
> 
> Will
> 
> On Sep 11, 2010, at 4:39 PM, Will M. Farr wrote:
> 
>> On Sep 11, 2010, at 4:20 PM, Robby Findler wrote:
>> 
>>> My laptop has a version of the tree
>>> from about 10 days ago and I'm not seeing any errors there. Is there
>>> something more that would help me reproduce this behavior?
>>> 
>>> Thanks,
>>> Robby
>> 
>> Huh.  Or maybe it's option 4: system/OS dependent.  I'm running on a Mac OS 10.6.4, Core 2 Duo system, compiling with gcc 4.2.1 (Apple version), in 64-bit mode (no gracket, since it doesn't work with 64-bit yet).  Configure options:
>> 
>> CFLAGS="-O3 -march=core2" CXXFLAGS="-O3 -march=core2" --enable-mac64 --disable-gracket --enable-places
>> 
>> I'm trying a build right now without the optimization options to the C compiler, and with places disabled; I'll let you know whether that fixes anything.  
>> 
>> I run the test suite using 
>> 
>> bin/racket collects/tests/run-automated-tests.rkt
>> 
>> from the top-level directory of the source repository (i.e. using the newly-build racket, not the one I have installed on my system).
>> 
>> Anything in this jumping out at you as the possible source of the problem?
>> 
>> Thanks,
>> Will
>