Re: [racket-users] Re: Organizing tests in project

I see, that explains it. Thank you for fixing it! On Wed, Apr 15, 2020 at 12:58 PM Matthew Flatt wrote: > The machine that formerly ran pkg-build died, so pkg-builds stopped for > a week or two. I moved eventually moved it to a new machine. Since I > had to start over with a v7.6 installer and

Re: [racket-users] Re: Organizing tests in project

The machine that formerly ran pkg-build died, so pkg-builds stopped for a week or two. I moved eventually moved it to a new machine. Since I had to start over with a v7.6 installer and the current catalog, all packages were re-built and re-tested. At Wed, 15 Apr 2020 12:14:31 -0700, Siddhartha Kas

[racket-users] Re: Organizing tests in project

This morning I find that the package referenced above no longer indicates failure. There haven't been any new commits, so it appears that the package rebuilt on its own without any fresh trigger -- but, notably, after a relatively long (weeks long) in

[racket-users] Re: Organizing tests in project

Hi, I'm still seeing an error on the Racket package server, but the build output is from March 31, 2019 and doesn't seem to be showing updated output. I gather that the server bui

[racket-users] Re: Organizing tests in project

FTR I fixed this by using the `compile-omit-paths` flag: https://docs.racket-lang.org/raco/setup-info.html E.g. in info.rkt: (define compile-omit-paths '("tests")) On Tue, Mar 17, 2020 at 12:25 PM Siddhartha Kasivajhula wrote: > Hi, > I'm attempting to organize tests in my package into subfo