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.
Re: [racket-users] Re: pkg-build report for the v6.2 release candidate
What happened was a new _documented_ export was added to `racket/match`: `match-define-values`. But yes, creating some dedicated test modules is a good idea so that this doesn't happen every release. Sam On Fri, May 15, 2015 at 3:28 AM Jack Firth wrote: > On Thursday, May 14, 2015 at 5:36:23 PM UTC-7, 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/ > > > > > > 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 > > doc-coverage is most likely failing because either 1) a new undocumented > export was added to racket/base, racket/list, racket/match, or > racket/syntax (I forget the exact ones it tests) or 2) an old undocumented > export was removed from one of those collections. Testing doc-coverage by > relying on the exports of racket collections instead of a specific testing > module was probably a bad idea. > > -- > 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] Environment Shuffling and 3D Syntax
At Fri, 15 May 2015 11:09:25 -0400, Philip Blair wrote: > One question I have is whether or > not the scopes feature is something which I can more or less count on being > available in future versions of Racket That's not yet clear. Although most existing code would be unaffected by the change to a set-of-scopes expander, there are significant compatibility issues. After posting an initial call for feedback on the dev list about a month ago, I've let the question sit while the v6.2 release is being prepared (and while I had other tasks to attend to). I think v6.2 is now far enough along that we could restart the conversation. -- 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] Environment Shuffling and 3D Syntax
Sorry for the delay (I was moving earlier this week). Thank you for taking a crack at the task. One question I have is whether or not the scopes feature is something which I can more or less count on being available in future versions of Racket (I understand that it's from a snapshot and might therefore undergo some changes before it would be released, but I would like to know if at least the functionality should be there). It may be a moot point in light of your syntactic solution, but I was wondering what the list's thoughts were on a partial implementation I came up with before you responded (it has the same "no macros" issue): I managed to get a runtime solution working using namespaces. Aside from macros, I believe that it implements most every feature the the CL package system does. There is a `*package*` parameter which is used to resolve unknown definitions (using an override of `#%top` which calls `namespace-variable-value` using the current package's namespace). I have attached the (somewhat messy) file for others to look at. What would be more racket-y/a better design approach: a more macro-oriented solution like what I was initially discussing and what Dr. Flatt wrote, or a more runtime-oriented solution like the (slightly messy) attached file (I'm not sure how to handle macros in that case, though...Maybe the list has some ideas :) )? Dr. Felleisen & Ryan: thank you for the link to that paper and webpage. The paper gave me the impression that I might be able to get some ideas from scmxlate. When I have a chance, I'll have to take a good look at the program itself. > On May 10, 2015, at 19:04, Matthias Felleisen wrote: > > Probably off-topic: you might be interested in > > http://repository.readscheme.org/ftp/papers/sw2003/Scmxlate.pdf > > Start with the title and then the summary at the end. Dorai has used this package to make his programs available in Schemes and Common Lisps. The PDF in question references a dead page for the software. The correct url is: http://www.ccs.neu.edu/home/dorai/scmxlate/index.html -- 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. package-rt.rkt Description: Binary data
[racket-users] Re: pkg-build report for the v6.2 release candidate
On Thursday, May 14, 2015 at 5:36:23 PM UTC-7, 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/ > > > 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 doc-coverage is most likely failing because either 1) a new undocumented export was added to racket/base, racket/list, racket/match, or racket/syntax (I forget the exact ones it tests) or 2) an old undocumented export was removed from one of those collections. Testing doc-coverage by relying on the exports of racket collections instead of a specific testing module was probably a bad idea. -- 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.
