Thank you Robby.
Good to know this.
On Sat, Jan 28, 2017 at 9:25 PM, Robby Findler
wrote:
> The pkg-build running here would pick up those changes, tho, so you
> could see the results:
>
> https://plt.eecs.northwestern.edu/pkg-build/
>
> It runs based on the
Thank you Matthew.
And, Racket will still be faster than my unstable packages.
On Sat, Jan 28, 2017 at 12:52 PM, Matthew Flatt wrote:
> That sounds like a reasonable addition to `raco test`, and I'll look
> into adding it soon. (The addition won't be effective in
>
The pkg-build running here would pick up those changes, tho, so you
could see the results:
https://plt.eecs.northwestern.edu/pkg-build/
It runs based on the latest snapshot (from
https://plt.eecs.northwestern.edu/snapshots/) instead of the release.
Robby
On Fri, Jan 27, 2017 at 10:52 PM,
That sounds like a reasonable addition to `raco test`, and I'll look
into adding it soon. (The addition won't be effective in
pkg-build.racket-lang.org until the next release, though.)
At Sat, 28 Jan 2017 11:23:44 +0800, WarGrey Gyoudmon Ju wrote:
> And also, I want to control `--check-stderr` in
At Fri, 27 Jan 2017 15:37:51 -0500, Stephen Chang wrote:
> I have a package whose tests are timing out when run by pkg-build. Is
> there a way to extend this timeout?
>
> I know I can specify individual file timeouts with `test-timeouts` but
> I couldnt figure out how to specify a timeout for
And also, I want to control `--check-stderr` in `info.rkt` file.
1. currently, typed racket complains any `ctype?` types and warns it to
stderr.
2. for some tests, display their output to stdout and stderr is more
convenient than wrapping the output into something like (check-exn?), say,
to see
I have a package whose tests are timing out when run by pkg-build. Is
there a way to extend this timeout?
I know I can specify individual file timeouts with `test-timeouts` but
I couldnt figure out how to specify a timeout for testing the whole
package. Is this possible?
Steve
--
You received
7 matches
Mail list logo