Re: [racket-users] pkg-build report for the v6.2 release candidate
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 .
John, is it stuck in moderation?
On Mon, May 18, 2015 at 9:46 AM, Sam Tobin-Hochstadt
wrote:
> I've now figured out what's going on here. The program in Greg's tests
> already has lexical context for the `{0 1 2}`, so it uses the `#%app` from
> that context, which gets the `racket` `#%app`. Normally, we'd just use
> s-exps instead of syntax objects as input to `eval`, since they don't have
> spurious lexical context, but that would lose the 'paren-shape property,
> which is crucial here. The solution, taken from the implementation of
> `racket/load`, is below:
>
> ```
> #lang racket
> (require syntax/strip-context)
> (current-namespace (make-base-namespace))
> (eval (namespace-syntax-introduce (strip-context #'(module m rackjure {0 1
> 2}
> ```
>
> Sam
>
> On Fri, May 15, 2015 at 3:47 PM Sam Tobin-Hochstadt
> wrote:
>>
>> It turns out that Greg's test was actually failing, but in a very strange
>> way. Having looked at this a bunch now, the issue seems to be that:
>>
>> ```
>> (check-exn exn:fail:syntax? (λ () (eval #'(module m rackjure {0 1 2}
>> ```
>>
>> Doesn't work inside a module, but it does work at the repl or in
>> `racket/load`. However, no namespace trickery that I've found will make it
>> work in a module.
>>
>> However, changing the syntax error to something different, such as
>> `(module m rackjure ())`, behaves as I would expect. Does `eval` +
>> `quote-syntax` do something strange with {} properties on syntax objects?
>>
>> Sam
>>
>> On Fri, May 15, 2015 at 1:53 PM Greg Hendershott
>> wrote:
>>>
>>> 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:
>>>
>>> (#
>>> 68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eval
>>> (syntax (module m rackjure (0 1 ...
>>>
>>> When I run the tests locally or on Travis CI, with `raco test -x .`,
>>> all pass including this.
>>>
>>> The message seems to be complaining that stderr is non-blank. But the
>>> test is check-exn. Is this an issue with the test environment not
>>> handling check-exn (a successful check-exn will write to stderr)?
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Racket Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to racket-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
>From the error at http://pkg-build.racket-lang.org/server/built/test-fail/pollen.txt is looks like the test depends on `racket` being in $PATH, but $PATH in the (intentionally minimal) pkg-build test environment doesn't include `racket`. You could use `find-exe` from `compiler/find-exe` to make the test independent of the $PATH setting. At Sun, 17 May 2015 12:22:43 -0700, Matthew Butterick 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 failure [1]. In my case, however, my test file [2] > does not use check-exn (though it does use `system`) > > > [1] > http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/serv > er/built/test-fail/pollen.txt > [2] https://github.com/mbutterick/pollen/blob/master/tests/test-langs.rkt > > On Fri, May 15, 2015 at 10:52 AM, Greg Hendershott < > greghendersh...@gmail.com> wrote: > > > 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: > > > > > (# kt> > > 68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eval > > (syntax (module m rackjure (0 1 ... > > > > When I run the tests locally or on Travis CI, with `raco test -x .`, > > all pass including this. > > > > The message seems to be complaining that stderr is non-blank. But the > > test is check-exn. Is this an issue with the test environment not > > handling check-exn (a successful check-exn will write to stderr)? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Racket Users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to racket-users+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
Rack test defines any stderr output to be a bug. Robby On Sunday, May 17, 2015, Matthew Butterick 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 failure [1]. In my case, however, my test file [2] > does not use check-exn (though it does use `system`) > > > [1] > http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/server/built/test-fail/pollen.txt > [2] https://github.com/mbutterick/pollen/blob/master/tests/test-langs.rkt > > On Fri, May 15, 2015 at 10:52 AM, Greg Hendershott < > greghendersh...@gmail.com > > wrote: > >> 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: >> >> (# >> 68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eval >> (syntax (module m rackjure (0 1 ... >> >> When I run the tests locally or on Travis CI, with `raco test -x .`, >> all pass including this. >> >> The message seems to be complaining that stderr is non-blank. But the >> test is check-exn. Is this an issue with the test environment not >> handling check-exn (a successful check-exn will write to stderr)? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Racket Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to racket-users+unsubscr...@googlegroups.com >> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com > > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
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] http://release-pkg-build.racket-lang.org.s3-website-us-west-2.amazonaws.com/server/built/test-fail/pollen.txt [2] https://github.com/mbutterick/pollen/blob/master/tests/test-langs.rkt On Fri, May 15, 2015 at 10:52 AM, Greg Hendershott < greghendersh...@gmail.com> wrote: > 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: > > (# > 68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eval > (syntax (module m rackjure (0 1 ... > > When I run the tests locally or on Travis CI, with `raco test -x .`, > all pass including this. > > The message seems to be complaining that stderr is non-blank. But the > test is check-exn. Is this an issue with the test environment not > handling check-exn (a successful check-exn will write to stderr)? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
At Fri, 15 May 2015 13:17:57 -0700, John Clements wrote: > > > On May 14, 2015, at 4:08 PM, Matthew Flatt 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 I’ve fixed these. Is there a plan to re-run these tests in a day or > two? The latest run uses package versions as of this morning (but the same candidate distribution). Thanks to package authors and help from Sam, it looks like 23 out of the 49 packages with newly reported dependency errors have been fixed already. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
> On May 14, 2015, at 4:08 PM, Matthew Flatt 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 I’ve fixed these. Is there a plan to re-run these tests in a day or two? John -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [racket-users] pkg-build report for the v6.2 release candidate
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: (# 68 2 2223 186)\nexpression: (check-exn exn:fail:syntax? (thunk (eval (syntax (module m rackjure (0 1 ... When I run the tests locally or on Travis CI, with `raco test -x .`, all pass including this. The message seems to be complaining that stderr is non-blank. But the test is check-exn. Is this an issue with the test environment not handling check-exn (a successful check-exn will write to stderr)? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[racket-users] pkg-build report for the v6.2 release candidate
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, and the problem is usually a missing dependency on "racket-doc". The new failures are a result improvements to the documentation dependency checker, not changes in the dependencies. (In other words, a dependency declaration was missing before, but it wasn't reported.) The 49 newly identified packages with dependency problems are listed below. Otherwise, two packages newly fail to install: bloggy --- an expected failure due to clean-up of an undocumented module munger --- looks like a bug in the release candidate, and we're investigating One package appears to have a new test failure: doc-coverage --- just needs test adjustments? Packages that have new dependency failures, almost always for "racket-doc": avl binary-class binary-class-mp3 check-sexp-equal describe dm dropbox ebml fast-convert finalizer fme gir grip heresy hyphenate icfp-2014-contracts-talk identikon levenshtein libscrypt libtoxcore-racket libuuid marketplace mboxrd-read midi-readwrite minikanren misc1 mischief-dev multipath-daemon nlopt osc pollen racket-eventfd racket-lang-org racquel rsvg rtmidi set sfont squicky sugar systemd tandem tasks txexpr typed-big-bang unicode-properties xexpr-path yotsubAPI zmq -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
