[racket-dev] What command should DrDr run by default?

From: Sam Tobin-Hochstadt (samth at ccs.neu.edu)
Date: Sat Jul 6 10:31:40 EDT 2013

These are now both done. Jay, if there's some bit of documentation I
missed, please let me know.

Sam

On Sat, Jul 6, 2013 at 10:03 AM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> I would say that if you know where to change, please go ahead.
>
> Robby
>
>
> On Sat, Jul 6, 2013 at 8:56 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
> wrote:
>>
>> Should I change the docs as well?  Or do you want to do that, Jay?
>>
>> On Sat, Jul 6, 2013 at 9:53 AM, Robby Findler
>> <robby at eecs.northwestern.edu> wrote:
>> > That's the plan. Thanks for fixing them.
>> >
>> > Robby
>> >
>> >
>> > On Sat, Jul 6, 2013 at 8:47 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
>> > wrote:
>> >>
>> >> I recently discovered that DrDr runs `raco test` by default on files,
>> >> and has since February. However, the DrDr documentation says that it
>> >> runs `racket -t`.  I discovered this because the change caused many of
>> >> the `net` tests to no longer actually run; see
>> >>
>> >>
>> >>
>> >> http://drdr.racket-lang.org/27042/pkgs/racket-pkgs/racket-test/tests/net/url.rkt
>> >>
>> >> which appears to be successful, even though running `racket` on that
>> >> file would have shown the error that I fixed in
>> >> https://github.com/plt/racket/commit/a4e529a816 . These tests are a
>> >> particularly bad case because they run all their tests in the `main`
>> >> submodule, and thus are *not* executed by `raco test`. If the plan is
>> >> for everything to run with `raco test`, I'll fix these tests.  But
>> >> what is the plan?
>> >>
>> >> Sam
>> >> _________________________
>> >>   Racket Developers list:
>> >>   http://lists.racket-lang.org/dev
>> >
>> >
>
>

Posted on the dev mailing list.