From: <fwi...@gm...> - 2015-04-21 05:43:35
|
Please test, especially if you can test on windows! We plan to keep this soft launch short, probably about 24 hours before we really release it. The releases: Installer: https://oss.sonatype.org/content/repositories/orgpython-1048/org/python/jython-installer/2.7-rc3/jython-installer-2.7-rc3.jar Standalone: https://oss.sonatype.org/content/repositories/orgpython-1049/org/python/jython-standalone/2.7-rc3/jython-standalone-2.7-rc3.jar The parent directories of each of the above have the checksums, source jars, javadocs, etc. -Frank |
From: Jeff A. <ja...@fa...> - 2015-04-21 20:28:21
|
I installed this on Win7x64 with Java 7u60. It installs fine and I ran regrtest -e. My bottom line was this: 23 fails unexpected: test___all__ test_classpathimporter test_file2k test_httpservers test_import test_import_pep328 test_jython_initializer test_netrc test_os_jy test_runpy test_select test_shutil test_slice test_slots_jy test_smtpnet test_socket test_ssl test_sys test_sys_jy test_tarfile test_urllib2 test_zipfile test_zipimport_jy These tests worked ok when re-run at the prompt: # test_select # test_slice # test_slots_jy # test_smtpnet The last three failed every time in regrtest -v -f, but with an ArrayIndexOutOfBoundsException in regrtest itself, rather than a proper test failure. Possibly I broke something when I worked on regrtest last, but why always these 3 tests? These 10 are known failures on the tracker: #2308 test___all__ #2309 test_classpathimporter #2312 test_file2k #2310 test_import #2314 test_shutil #2315 test_ssl #2312 test_sys_jy #2316 test_tarfile #2317 test_urllib2 #2318 test_zipimport_jy These failed solidly in regrtest and at the prompt but are not (I think) on the tracker. They are not all new, and some have been called flakey. A couple are just unlink errors. test_httpservers # bad file descriptor test_import_pep328 test_jython_initializer test_netrc test_os_jy test_runpy # unlink() error test_socket test_sys test_zipfile # unlink() errors Jeff On 21/04/2015 06:43, fwi...@gm... wrote: > Please test, especially if you can test on windows! We plan to keep > this soft launch short, probably about 24 hours before we really > release it. > > The releases: > > Installer: https://oss.sonatype.org/content/repositories/orgpython-1048/org/python/jython-installer/2.7-rc3/jython-installer-2.7-rc3.jar > > Standalone: https://oss.sonatype.org/content/repositories/orgpython-1049/org/python/jython-standalone/2.7-rc3/jython-standalone-2.7-rc3.jar > > The parent directories of each of the above have the checksums, source > jars, javadocs, etc. > > -Frank > |
From: Jeff A. <ja...@fa...> - 2015-04-21 22:18:53
|
And on Java 8u45 these additional failures, repeatable at the prompt: test_bz2 test_list_jy test_marshal Jeff On 21/04/2015 21:27, Jeff Allen wrote: > I installed this on Win7x64 with Java 7u60. It installs fine and I ran > regrtest -e. My bottom line was this: > > 23 fails unexpected: > test___all__ test_classpathimporter test_file2k test_httpservers > test_import test_import_pep328 test_jython_initializer test_netrc > test_os_jy test_runpy test_select test_shutil test_slice > test_slots_jy test_smtpnet test_socket test_ssl test_sys > test_sys_jy test_tarfile test_urllib2 test_zipfile > test_zipimport_jy > > These tests worked ok when re-run at the prompt: > # test_select > # test_slice > # test_slots_jy > # test_smtpnet > The last three failed every time in regrtest -v -f, but with an > ArrayIndexOutOfBoundsException in regrtest itself, rather than a proper > test failure. Possibly I broke something when I worked on regrtest last, > but why always these 3 tests? > > These 10 are known failures on the tracker: > #2308 test___all__ > #2309 test_classpathimporter > #2312 test_file2k > #2310 test_import > #2314 test_shutil > #2315 test_ssl > #2312 test_sys_jy > #2316 test_tarfile > #2317 test_urllib2 > #2318 test_zipimport_jy > > These failed solidly in regrtest and at the prompt but are not (I think) > on the tracker. They are not all new, and some have been called flakey. > A couple are just unlink errors. > test_httpservers # bad file descriptor > test_import_pep328 > test_jython_initializer > test_netrc > test_os_jy > test_runpy # unlink() error > test_socket > test_sys > test_zipfile # unlink() errors > > > Jeff > > On 21/04/2015 06:43, fwi...@gm... wrote: >> Please test, especially if you can test on windows! We plan to keep >> this soft launch short, probably about 24 hours before we really >> release it. >> >> The releases: >> >> Installer: https://oss.sonatype.org/content/repositories/orgpython-1048/org/python/jython-installer/2.7-rc3/jython-installer-2.7-rc3.jar >> >> Standalone: https://oss.sonatype.org/content/repositories/orgpython-1049/org/python/jython-standalone/2.7-rc3/jython-standalone-2.7-rc3.jar >> >> The parent directories of each of the above have the checksums, source >> jars, javadocs, etc. >> >> -Frank >> > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > > |
From: Jim B. <jim...@py...> - 2015-04-21 23:23:05
|
Jeff, I have seen test_bytes fail with ArrayIndexOutOfBoundsException in the test_repeat case, which is testing out of memory scenarios. Although it would be best not to see Java exceptions leak out to Python code in this case, we have reported bugs for similar "leakiness" that we have triaged to 2.7.1. Given that existing triage, this means we haven't seen anything yet to hold the release. Frank, looks like we are good for a RC3 final, so we can get the testing we need. - Jim On Tue, Apr 21, 2015 at 4:18 PM, Jeff Allen <ja...@fa...> wrote: > And on Java 8u45 these additional failures, repeatable at the prompt: > > test_bz2 > test_list_jy > test_marshal > > Jeff > > On 21/04/2015 21:27, Jeff Allen wrote: > > I installed this on Win7x64 with Java 7u60. It installs fine and I ran > > regrtest -e. My bottom line was this: > > > > 23 fails unexpected: > > test___all__ test_classpathimporter test_file2k test_httpservers > > test_import test_import_pep328 test_jython_initializer test_netrc > > test_os_jy test_runpy test_select test_shutil test_slice > > test_slots_jy test_smtpnet test_socket test_ssl test_sys > > test_sys_jy test_tarfile test_urllib2 test_zipfile > > test_zipimport_jy > > > > These tests worked ok when re-run at the prompt: > > # test_select > > # test_slice > > # test_slots_jy > > # test_smtpnet > > The last three failed every time in regrtest -v -f, but with an > > ArrayIndexOutOfBoundsException in regrtest itself, rather than a proper > > test failure. Possibly I broke something when I worked on regrtest last, > > but why always these 3 tests? > > > > These 10 are known failures on the tracker: > > #2308 test___all__ > > #2309 test_classpathimporter > > #2312 test_file2k > > #2310 test_import > > #2314 test_shutil > > #2315 test_ssl > > #2312 test_sys_jy > > #2316 test_tarfile > > #2317 test_urllib2 > > #2318 test_zipimport_jy > > > > These failed solidly in regrtest and at the prompt but are not (I think) > > on the tracker. They are not all new, and some have been called flakey. > > A couple are just unlink errors. > > test_httpservers # bad file descriptor > > test_import_pep328 > > test_jython_initializer > > test_netrc > > test_os_jy > > test_runpy # unlink() error > > test_socket > > test_sys > > test_zipfile # unlink() errors > > > > > > Jeff > |
From: <fwi...@gm...> - 2015-04-22 15:54:09
|
On Tue, Apr 21, 2015 at 4:22 PM, Jim Baker <jim...@py...> wrote: > Jeff, I have seen test_bytes fail with ArrayIndexOutOfBoundsException in the > test_repeat case, which is testing out of memory scenarios. Although it > would be best not to see Java exceptions leak out to Python code in this > case, we have reported bugs for similar "leakiness" that we have triaged to > 2.7.1. Given that existing triage, this means we haven't seen anything yet > to hold the release. > > Frank, looks like we are good for a RC3 final, so we can get the testing we > need. > Released! Sorry for the delay, it takes a few hours to get to the maven repo after I push the buttons, and I did that fairly late. -Frank |
From: Jeff A. <ja...@fa...> - 2015-04-22 06:58:33
|
It wasn't a stop the launch message, just reporting what I saw. I'm happy to go with others' judgement. I am *instinctively* a bit uncomfortable that anything go out with failing or skipped tests. But my instincts have been shaped by the sort of subjects where just one counterexample proves you wrong, *not* by much experience launching software products. I'm interested in how this level of test conformance maps to user experience. I think Jython is pretty good now and that we won't be buried in bug reports. I'd like to see testing give us a clearer result. At the moment it always fails and you have to work out what kind of failure to know where you stand. On the one hand I think defects should be visible and painful; on the other I'd like to have a test that only shouts when something unexpected happens. (And I'd like a build bot to do the shouting.) Now I understand regrtest better (since the weekend!), and which parts we added, I think it offers a way of saying "everything is as expected (but don't forget these problems)", vs. "you just broke something", with only the latter being shouted. It's nearly there. Jeff Allen On 22/04/2015 00:22, Jim Baker wrote: > Jeff, I have seen test_bytes fail with ArrayIndexOutOfBoundsException > in the test_repeat case, which is testing out of memory scenarios. > Although it would be best not to see Java exceptions leak out to > Python code in this case, we have reported bugs for similar > "leakiness" that we have triaged to 2.7.1. Given that existing triage, > this means we haven't seen anything yet to hold the release. > > Frank, looks like we are good for a RC3 final, so we can get the > testing we need. > > - Jim > > On Tue, Apr 21, 2015 at 4:18 PM, Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > And on Java 8u45 these additional failures, repeatable at the prompt: > > test_bz2 > test_list_jy > test_marshal > > Jeff > > On 21/04/2015 21:27, Jeff Allen wrote: > > I installed this on Win7x64 with Java 7u60. It installs fine and > I ran > > regrtest -e. My bottom line was this: > > > > 23 fails unexpected: > > test___all__ test_classpathimporter test_file2k > test_httpservers > > test_import test_import_pep328 test_jython_initializer > test_netrc > > test_os_jy test_runpy test_select test_shutil test_slice > > test_slots_jy test_smtpnet test_socket test_ssl test_sys > > test_sys_jy test_tarfile test_urllib2 test_zipfile > > test_zipimport_jy > > > > These tests worked ok when re-run at the prompt: > > # test_select > > # test_slice > > # test_slots_jy > > # test_smtpnet > > The last three failed every time in regrtest -v -f, but with an > > ArrayIndexOutOfBoundsException in regrtest itself, rather than a > proper > > test failure. Possibly I broke something when I worked on > regrtest last, > > but why always these 3 tests? > > > > These 10 are known failures on the tracker: > > #2308 test___all__ > > #2309 test_classpathimporter > > #2312 test_file2k > > #2310 test_import > > #2314 test_shutil > > #2315 test_ssl > > #2312 test_sys_jy > > #2316 test_tarfile > > #2317 test_urllib2 > > #2318 test_zipimport_jy > > > > These failed solidly in regrtest and at the prompt but are not > (I think) > > on the tracker. They are not all new, and some have been called > flakey. > > A couple are just unlink errors. > > test_httpservers # bad file descriptor > > test_import_pep328 > > test_jython_initializer > > test_netrc > > test_os_jy > > test_runpy # unlink() error > > test_socket > > test_sys > > test_zipfile # unlink() errors > > > > > > Jeff > |
From: Jim B. <jim...@py...> - 2015-04-22 15:56:56
|
On Wed, Apr 22, 2015 at 12:58 AM, Jeff Allen <ja...@fa...> wrote: > It wasn't a stop the launch message, just reporting what I saw. I'm happy > to go with others' judgement. > My feeling is that we are complete for 2.7.0, but we will not know until users start trying this release out on their own code, first with a final RC3 and then the final release itself. Right now, we are running any number of tests code that attempts to push various limits, often to ensure that CPython will not crash with a segfault. But on Jython, this is hard - if not impossible! - to do. (I have seen only one crash FWIW in the last two years, in Clamp's use of Java classes, through JNI, for writing jars. So nothing Jython could have prevented in any event.) So IMHO having a test report back a failure that could be wrapped better as a Python exception is OK. > > I am *instinctively* a bit uncomfortable that anything go out with failing > or skipped tests. But my instincts have been shaped by the sort of subjects > where just one counterexample proves you wrong, *not* by much experience > launching software products. I'm interested in how this level of test > conformance maps to user experience. I think Jython is pretty good now and > that we won't be buried in bug reports. > We still have 229 open bugs... so it's just a question of having even more ;) There will always be more for any successful project with some level of complexity, which Jython obviously exceeds by some a couple of orders of magnitude or so. (Well at least without formal verification methods...) > I'd like to see testing give us a clearer result. At the moment it always > fails and you have to work out what kind of failure to know where you > stand. On the one hand I think defects should be visible and painful; on > the other I'd like to have a test that only shouts when something > unexpected happens. (And I'd like a build bot to do the shouting.) Now I > understand regrtest better (since the weekend!), and which parts we added, > I think it offers a way of saying "everything is as expected (but don't > forget these problems)", vs. "you just broke something", with only the > latter being shouted. It's nearly there. > Agreed! A major goal of 2.7.1 should be make our tools work better for us, whether that's migrating to https://github.com/jython; moving to Maven-driven bhttps://github.com/jythonuilds (but still using Ant for driving pieces like Antlr); and having CI with Travis, including on all PRs. - Jim |
From: <fwi...@gm...> - 2015-04-22 15:58:47
|
On Tue, Apr 21, 2015 at 11:58 PM, Jeff Allen <ja...@fa...> wrote: > It wasn't a stop the launch message, just reporting what I saw. I'm happy to > go with others' judgement. > > I am *instinctively* a bit uncomfortable that anything go out with failing > or skipped tests. But my instincts have been shaped by the sort of subjects > where just one counterexample proves you wrong, *not* by much experience > launching software products. I'm interested in how this level of test > conformance maps to user experience. I think Jython is pretty good now and > that we won't be buried in bug reports. > > I'd like to see testing give us a clearer result. At the moment it always > fails and you have to work out what kind of failure to know where you stand. > On the one hand I think defects should be visible and painful; on the other > I'd like to have a test that only shouts when something unexpected happens. > (And I'd like a build bot to do the shouting.) Now I understand regrtest > better (since the weekend!), and which parts we added, I think it offers a > way of saying "everything is as expected (but don't forget these problems)", > vs. "you just broke something", with only the latter being shouted. It's > nearly there. You are totally right Jeff, getting a clean regression test is the goal, and I think we are getting close. Some kind of built bot would be even better :) It should be very doable in the 2.7.x series. With the 3.x series I hope to go even further and someday have build bots that actually track changes in the standard CPython library as they come in. Well, I can dream can't I? :) -Frank |
From: Jim B. <jim...@py...> - 2015-04-22 16:13:31
|
It's worth bearing in mind that not even CPython regrtest always build cleanly on their buildbots, whether it is 2.7, 3.4, or 3.5. See http://buildbot.python.org/all/waterfall?category=2.7.stable&category=3.4.stable&category=3.x.stable This was part of the discussion at the Python Language Summit two weeks ago at PyCon with respect to CPython dev workflow. On Wed, Apr 22, 2015 at 9:58 AM, fwi...@gm... < fwi...@gm...> wrote: > On Tue, Apr 21, 2015 at 11:58 PM, Jeff Allen <ja...@fa...> wrote: > > It wasn't a stop the launch message, just reporting what I saw. I'm > happy to > > go with others' judgement. > > > > I am *instinctively* a bit uncomfortable that anything go out with > failing > > or skipped tests. But my instincts have been shaped by the sort of > subjects > > where just one counterexample proves you wrong, *not* by much experience > > launching software products. I'm interested in how this level of test > > conformance maps to user experience. I think Jython is pretty good now > and > > that we won't be buried in bug reports. > > > > I'd like to see testing give us a clearer result. At the moment it always > > fails and you have to work out what kind of failure to know where you > stand. > > On the one hand I think defects should be visible and painful; on the > other > > I'd like to have a test that only shouts when something unexpected > happens. > > (And I'd like a build bot to do the shouting.) Now I understand regrtest > > better (since the weekend!), and which parts we added, I think it offers > a > > way of saying "everything is as expected (but don't forget these > problems)", > > vs. "you just broke something", with only the latter being shouted. It's > > nearly there. > You are totally right Jeff, getting a clean regression test is the > goal, and I think we are getting close. Some kind of built bot would > be even better :) It should be very doable in the 2.7.x series. > > With the 3.x series I hope to go even further and someday have build > bots that actually track changes in the standard CPython library as > they come in. Well, I can dream can't I? :) > > -Frank > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |