Re: [Jython-dev] Putting 2.7.1 beta 1 together tomorrow (Thur Sept 10)

[Jeff A. <ja...@fa...>]

Welcome to the list Adam.

I'm definitely for this in principle, and will kick the tyres on it. I'm 
in favour of tests that pass, so we can tell immediately what we've 
broken, raising the possibility of having a useful build bot again.

I'm against turning off the things that tell us we've got work to do. 
regrtest is quite good, however, in gently reproaching you each time 
with a list of what you're ignoring. I suggest things we add to the 
expected failures list, if they are indeed applicable to a platform, 
should each be made issues at that point, and the fix should include 
putting the test back.

Skips at the test case or test method level tend to be invisible. Jim 
has sometimes mined the tests to make a list of those, to work off as 
issues. Some kind of automatic list would be nice, again distinguishing 
"should work" from "not applicable to Jython".

Jeff Allen

On 10/09/2015 16:18, Adam Burke wrote:
> I have uploaded a small patch to clean up regression tests on windows. 
> It doesn't actually do much to fix the tests, it just marks expected 
> failures and skips correctly, at least on my machine. I mainly thought 
> it would make build testing simpler if we could see clear green results.
>
> http://bugs.jython.org/issue2393
>
> If people find the idea useful, we could use it for regression tests 
> of the 2.7.1 release candidates on different platforms on the same lines.
>
> It's a first patch so I might have stepped on some conventions or 
> missed something about the current tests, though. Feedback welcome.
>
> Cheers
> Adam
>
> On 10 September 2015 at 14:32, Jeff Allen <ja...@fa... 
> <mailto:ja...@fa...>> wrote:
>
>     I'm still hoping to push a fix for Issue 2364 (where a Latin-1
>     interpretation is incorrectly given to ascii bytes). It will be
>     close: my fault for stopping to prove I was not making PyString
>     any slower!
>
>     Jeff
>
>
>     On 09/09/2015 20:24, Jim Baker wrote:
>>     Per my previous thread
>>     (http://python.6.x6.nabble.com/Planning-the-Jython-2-7-1-release-td5168866.html),
>>     we will be putting together the beta 1 for 2.7.1 tomorrow. If you
>>     have any last minute commits that are ready, now is a great time
>>     to get them in for user testing of this beta.
>>
>>     In terms of specific timing, we are looking at the evening with
>>     respect to America/Los_Angeles
>>     <https://en.wikipedia.org/wiki/America/Los_Angeles>, since that's
>>     a convenient time for Frank. Respond here if you need this date
>>     to slip for any reason.
>>
>>     - Jim
>>
>>
>
>
>     ------------------------------------------------------------------------------
>     Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>     Get real-time metrics from all of your servers, apps and tools
>     in one place.
>     SourceForge users - Click here to start your Free Trial of Datadog
>     now!
>     http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>     _______________________________________________
>     Jython-dev mailing list
>     Jyt...@li...
>     <mailto:Jyt...@li...>
>     https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>