1. Thanks for figuring this out!
2. I'm pushing a commit to utilize this.
3. I wanted to link to your post in my commit message -- but I can't.
When I type this, your post isn't showing up in the Google Groups UI
for this thread --
https://groups.google.com/forum/#!topic/racket-users/ANgDaNplOBc
At Fri, 15 May 2015 13:17:57 -0700, John Clements wrote:
On May 14, 2015, at 4:08 PM, Matthew Flatt mfl...@cs.utah.edu wrote:
Here are the results of a package build using the v6.2 release
candidate:
http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/
FWIW I've had the same problem. Even though 'raco test -p pollen' shows no
errors locally nor on Travis CI, the Racket build system produces a
non-empty stderr test failure [1]. In my case, however, my test file [2]
does not use check-exn (though it does use `system`)
[1]
Rack test defines any stderr output to be a bug.
Robby
On Sunday, May 17, 2015, Matthew Butterick m...@mbtype.com wrote:
FWIW I've had the same problem. Even though 'raco test -p pollen' shows no
errors locally nor on Travis CI, the Racket build system produces a
non-empty stderr test
This is OT wrt deps and doc, but:
I don't understand this reported test failure for rackjure, on both
versions of Racket:
test.rkt: raco test: non-empty stderr:
#\nFAILURE\nname: check-exn\nlocation:
On May 14, 2015, at 4:08 PM, Matthew Flatt mfl...@cs.utah.edu wrote:
Here are the results of a package build using the v6.2 release
candidate:
http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/
Compare to v6.1.1:
http://pkg-build.racket-lang.org/
I believe
Here are the results of a package build using the v6.2 release
candidate:
http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/
Compare to v6.1.1:
http://pkg-build.racket-lang.org/
For the v6.2 candidate, there are lots of dependency failures related
to documentation,
7 matches
Mail list logo