[racket-dev] Pre-Release Checklist for v6.0.1

From: Neil Toronto (neil.toronto at gmail.com)
Date: Thu Apr 24 12:52:37 EDT 2014

I found out that it happens when a polygon is just three collinear or 
nearly collinear points, and the polygon's "plane," which is degenerate, 
is somehow the best choice for a BSP split.

I still haven't gotten the upcoming release's Plot to generate a 
collection of shapes that causes nontermination. I'll just push the fix 
I used in my dev branch, which detects degenerate planes and calls the 
failure continuation to try the next plane. The BSP tree build should 
have been sanitizing its inputs like that anyway.

Doug, have you seen nontermination in your tests?

Neil ⊥

On 04/18/2014 02:54 PM, Robby Findler wrote:
> That sounds like a good plan to me. Let us know what you find out.
>
> Robby
>
> On Fri, Apr 18, 2014 at 3:47 PM, Neil Toronto <neil.toronto at gmail.com> wrote:
>> On 04/17/2014 04:44 PM, Ryan Culpepper wrote:
>>>
>>> * Neil Toronto <neil.toronto at gmail.com>
>>>     - Plot Tests
>>>     - Images Tests
>>>     - Inspect icons
>>>     - Math tests
>>
>>
>> I found an infinite loop in Plot's new 3D engine, but I've only been able to
>> replicate it using a randomized test case for a feature I haven't pushed
>> yet. Even though that feature won't be in the upcoming release, there's
>> definitely an error in the 3D engine that I don't want users stumbling into.
>>
>> If the Powers That Be don't mind, I'll concentrate on finding a repeatable
>> test case, and check the rest of my list at the second call.
>>
>> Neil ⊥
>>
>>
>> _________________________
>>   Racket Developers list:
>>   http://lists.racket-lang.org/dev


Posted on the dev mailing list.