<div dir="ltr">I think those are already planned to be taken. So lets see if the tests pass in the next build.<div><br></div><div>Robby</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 24, 2013 at 9:55 PM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If we just take the latter 3 commits that Vincent mentioned, it should<br>
fix the (serial) tests. Those are just TR test fixes, and can't break<br>
anything else.<br>
<br>
Sam<br>
<br>
On Wed, Jul 24, 2013 at 10:54 PM, Robby Findler<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote:<br>
> I don't think we should take that commit. Is it possible to get a version of<br>
> the TR tests that either don't run in parallel or run without passing<br>
> keywords across place channels?<br>
><br>
> Robby<br>
><br>
><br>
><br>
> On Wed, Jul 24, 2013 at 9:41 PM, Sam Tobin-Hochstadt <<a href="mailto:samth@ccs.neu.edu">samth@ccs.neu.edu</a>><br>
> wrote:<br>
>><br>
>> I will say that I'm not 100% happy with just assuming that TR works in<br>
>> the absence of a clean test run. Is there a reason not to include<br>
>> these fixes?<br>
>><br>
>> Sam<br>
>><br>
>> On Wed, Jul 24, 2013 at 5:15 PM, Robby Findler<br>
>> <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote:<br>
>> > Thanks.<br>
>> ><br>
>> > Robby<br>
>> ><br>
>> ><br>
>> > On Wed, Jul 24, 2013 at 3:19 PM, Vincent St-Amour <<a href="mailto:stamourv@ccs.neu.edu">stamourv@ccs.neu.edu</a>><br>
>> > wrote:<br>
>> >><br>
>> >> The problems I've observed were only with the tests.<br>
>> >><br>
>> >> The first problem I reported was caused by a bug/limitation in places,<br>
>> >> which was fixed by 733907474190da499a1782b230086170c5b87643. It was<br>
>> >> preventing the TR test suite from running properly.<br>
>> >><br>
>> >> The others were bugs in the TR tests, not in TR itself.<br>
>> >><br>
>> >> TR itself should be fine for the release.<br>
>> >><br>
>> >> Vincent<br>
>> >><br>
>> >><br>
>> >><br>
>> >> At Wed, 24 Jul 2013 15:03:08 -0500,<br>
>> >> Robby Findler wrote:<br>
>> >> ><br>
>> >> > [1 <text/plain; UTF-8 (7bit)>]<br>
>> >> > Vincent: can you clarify what the status of TR & the release is,<br>
>> >> > please?<br>
>> >> > Are there problems only with tests, or were there problems elsewhere<br>
>> >> > too?<br>
>> >> ><br>
>> >> > Thanks,<br>
>> >> > Robby<br>
>> >> ><br>
>> >> ><br>
>> >> > On Tue, Jul 23, 2013 at 9:11 AM, Vincent St-Amour<br>
>> >> > <<a href="mailto:stamourv@ccs.neu.edu">stamourv@ccs.neu.edu</a>>wrote:<br>
>> >> ><br>
>> >> > > The TR tests still fail when using a single place.<br>
>> >> > ><br>
>> >> > > The following commits should be included in the release:<br>
>> >> > > 069ff59a4bd6a988a5670c7e4dd38c1dbbe12ec0<br>
>> >> > > 0e7940ab4943600e6f5c8f13ce7ee13e8af9a8f5<br>
>> >> > > ab5075bc762356f86bb7dfd34dac8d24ada1a140<br>
>> >> > ><br>
>> >> > > Vincent<br>
>> >> > ><br>
>> >> > ><br>
>> >> > ><br>
>> >> > > At Mon, 22 Jul 2013 17:49:20 -0400,<br>
>> >> > > Vincent St-Amour wrote:<br>
>> >> > > ><br>
>> >> > > > At Mon, 22 Jul 2013 15:13:28 -0400,<br>
>> >> > > > Ryan Culpepper wrote:<br>
>> >> > > > ><br>
>> >> > > > > Checklist items for the v5.3.6 release<br>
>> >> > > > > (using the v5.3.5.900 release candidate build)<br>
>> >> > > > ><br>
>> >> > > > > Search for your name to find relevant items, reply when you<br>
>> >> > > > > finish<br>
>> >> > > > > an<br>
>> >> > > > > item (please indicate which item/s is/are done). Also, if you<br>
>> >> > > > > have any<br>
>> >> > > > > commits that should have been picked, make sure that the<br>
>> >> > > > > changes<br>
>> >> > > > > are<br>
>> >> > > in.<br>
>> >> > > > ><br>
>> >> > > > > Important: new builds are created without announcement, usually<br>
>> >> > > whenever<br>
>> >> > > > > I pick a few commits. If you need to commit changes, please<br>
>> >> > > > > make<br>
>> >> > > > > sure<br>
>> >> > > > > you tell me to pick it into the release branch.<br>
>> >> > > > ><br>
>> >> > > > > --> Release candidates are at<br>
>> >> > > > > --> <a href="http://pre.racket-lang.org/release/installers" target="_blank">http://pre.racket-lang.org/release/installers</a><br>
>> >> > > ><br>
>> >> > > > The "Linux/i386/Ubuntu Precise" installer is 64 bits, which is<br>
>> >> > > > wrong.<br>
>> >> > > ><br>
>> >> > > > > * Sam Tobin-Hochstadt <<a href="mailto:samth@ccs.neu.edu">samth@ccs.neu.edu</a>>,<br>
>> >> > > > > Vincent St-Amour <<a href="mailto:stamourv@ccs.neu.edu">stamourv@ccs.neu.edu</a>><br>
>> >> > > > > - Match Tests<br>
>> >> > > > > - Typed Racket Tests<br>
>> >> > > > > - Typed Racket Updates: update HISTORY<br>
>> >> > > > > (updates should show v5.3.6 as the most current version;<br>
>> >> > > > > email<br>
>> >> > > > > me<br>
>> >> > > > > to pick the changes when they're done, or tell me if there<br>
>> >> > > > > are<br>
>> >> > > > > no<br>
>> >> > > such<br>
>> >> > > > > changes.)<br>
>> >> > > ><br>
>> >> > > > I get the following error when runing the TR tests:<br>
>> >> > > ><br>
>> >> > > > place-channel-put: value not allowed in a message<br>
>> >> > > > value: '#:methods<br>
>> >> > > > ...<br>
>> >> > > ><br>
>> >> > > > Is 733907474190da499a1782b230086170c5b87643 missing from the<br>
>> >> > > > release?<br>
>> >> > > ><br>
>> >> > > > Now running the tests without places.<br>
>> >> > > ><br>
>> >> > > > Vincent<br>
>> >> > > _________________________<br>
>> >> > > Racket Developers list:<br>
>> >> > > <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
>> >> > ><br>
>> >> > [2 <text/html; UTF-8 (quoted-printable)>]<br>
>> >> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > _________________________<br>
>> > Racket Developers list:<br>
>> > <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br></div>