[racket-dev] Compiling tests

This has caused me some trouble and I'm not sure it is a good way to go, in
general. Specifically, I'd like to think that our newer tests will more and
more be things we'd want to compile.

My desire to compile the tests is the same reason I want to compile any
Racket file: so it loads faster.

So, I'd like to go back to the old way: I can try disabling eopl tests and
look at any other problematic collections if that would help with your
original concern in a different way.

Robby

On Friday, March 9, 2012, Eli Barzilay wrote:

> Does anyone mind avoiding compilation of `collects/tests/*'?
>
> I'm counting now about 10% of the tree build time spent on compiling
> stuff in collects/tests.  Probably a large part of that is the eopl
> tests, since most of the other big tests already disable compilation.
> I could just add the info file to avoid compiling the eopl tests, but
> I prefer to just disable compilation of all of collects/tests, so that
> future additions will not need to be dealt with individually.  In the
> past there were objections to doing that because compiling the tests
> has some testing value too -- but it seems that drdr is now completely
> filling that role.
>
> --
>          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
>                    http://barzilay.org/                   Maze is Life!
> _________________________
>  Racket Developers list:
>  http://lists.racket-lang.org/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20120329/e2a32f82/attachment.html>