Menu
▾
▴
jython-dev — Discussion of developing and enhancing Jython itself(!) (not how to use Jython)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(38) |
Nov
(98) |
Dec
(58) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(114) |
Feb
(123) |
Mar
(96) |
Apr
(66) |
May
(84) |
Jun
(72) |
Jul
(128) |
Aug
(126) |
Sep
(82) |
Oct
(80) |
Nov
(148) |
Dec
(55) |
| 2002 |
Jan
(137) |
Feb
(85) |
Mar
(118) |
Apr
(67) |
May
(71) |
Jun
(28) |
Jul
(69) |
Aug
(48) |
Sep
(83) |
Oct
(79) |
Nov
(54) |
Dec
(32) |
| 2003 |
Jan
(44) |
Feb
(47) |
Mar
(59) |
Apr
(57) |
May
(43) |
Jun
(45) |
Jul
(44) |
Aug
(39) |
Sep
(27) |
Oct
(62) |
Nov
(17) |
Dec
(23) |
| 2004 |
Jan
(41) |
Feb
(51) |
Mar
(38) |
Apr
(30) |
May
(25) |
Jun
(12) |
Jul
(11) |
Aug
(27) |
Sep
(16) |
Oct
(56) |
Nov
(23) |
Dec
(29) |
| 2005 |
Jan
(75) |
Feb
(82) |
Mar
(50) |
Apr
(77) |
May
(19) |
Jun
(104) |
Jul
(47) |
Aug
(42) |
Sep
(28) |
Oct
(143) |
Nov
(62) |
Dec
(13) |
| 2006 |
Jan
(20) |
Feb
(10) |
Mar
(59) |
Apr
(45) |
May
(25) |
Jun
(129) |
Jul
(162) |
Aug
(91) |
Sep
(15) |
Oct
(39) |
Nov
(186) |
Dec
(191) |
| 2007 |
Jan
(134) |
Feb
(140) |
Mar
(106) |
Apr
(77) |
May
(92) |
Jun
(63) |
Jul
(233) |
Aug
(102) |
Sep
(119) |
Oct
(63) |
Nov
(68) |
Dec
(32) |
| 2008 |
Jan
(69) |
Feb
(91) |
Mar
(129) |
Apr
(44) |
May
(18) |
Jun
(53) |
Jul
(50) |
Aug
(25) |
Sep
(11) |
Oct
(28) |
Nov
(67) |
Dec
(36) |
| 2009 |
Jan
(20) |
Feb
(24) |
Mar
(66) |
Apr
(53) |
May
(48) |
Jun
(48) |
Jul
(59) |
Aug
(82) |
Sep
(49) |
Oct
(30) |
Nov
(16) |
Dec
(16) |
| 2010 |
Jan
(52) |
Feb
(25) |
Mar
(36) |
Apr
(34) |
May
(14) |
Jun
(15) |
Jul
(14) |
Aug
(16) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(22) |
Mar
(45) |
Apr
(9) |
May
(8) |
Jun
(13) |
Jul
(12) |
Aug
(4) |
Sep
(6) |
Oct
(10) |
Nov
(21) |
Dec
(5) |
| 2012 |
Jan
(6) |
Feb
(9) |
Mar
(25) |
Apr
(6) |
May
(4) |
Jun
(23) |
Jul
(6) |
Aug
(18) |
Sep
(21) |
Oct
(34) |
Nov
(19) |
Dec
(25) |
| 2013 |
Jan
(8) |
Feb
(34) |
Mar
(35) |
Apr
(4) |
May
(11) |
Jun
(4) |
Jul
(7) |
Aug
(5) |
Sep
(20) |
Oct
(12) |
Nov
(11) |
Dec
(7) |
| 2014 |
Jan
(10) |
Feb
(18) |
Mar
(50) |
Apr
(26) |
May
(53) |
Jun
(21) |
Jul
(12) |
Aug
(39) |
Sep
(43) |
Oct
(26) |
Nov
(8) |
Dec
(6) |
| 2015 |
Jan
(18) |
Feb
(32) |
Mar
(31) |
Apr
(42) |
May
(38) |
Jun
(13) |
Jul
(6) |
Aug
(11) |
Sep
(29) |
Oct
(25) |
Nov
(10) |
Dec
(11) |
| 2016 |
Jan
(24) |
Feb
(12) |
Mar
(13) |
Apr
(15) |
May
(22) |
Jun
(8) |
Jul
(12) |
Aug
(25) |
Sep
(8) |
Oct
(6) |
Nov
(13) |
Dec
(7) |
| 2017 |
Jan
(6) |
Feb
(29) |
Mar
(32) |
Apr
(8) |
May
(82) |
Jun
(42) |
Jul
(20) |
Aug
(17) |
Sep
(27) |
Oct
(14) |
Nov
(22) |
Dec
(6) |
| 2018 |
Jan
(12) |
Feb
(9) |
Mar
(22) |
Apr
(19) |
May
(14) |
Jun
(9) |
Jul
(9) |
Aug
(22) |
Sep
(22) |
Oct
(12) |
Nov
(13) |
Dec
(8) |
| 2019 |
Jan
(22) |
Feb
(3) |
Mar
(30) |
Apr
(20) |
May
(20) |
Jun
(6) |
Jul
(15) |
Aug
(25) |
Sep
(11) |
Oct
(24) |
Nov
(11) |
Dec
(6) |
| 2020 |
Jan
(9) |
Feb
(12) |
Mar
(29) |
Apr
(10) |
May
(22) |
Jun
(11) |
Jul
(15) |
Aug
(5) |
Sep
(6) |
Oct
(7) |
Nov
(7) |
Dec
(13) |
| 2021 |
Jan
(21) |
Feb
(5) |
Mar
(5) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(6) |
Aug
(8) |
Sep
(5) |
Oct
(9) |
Nov
(5) |
Dec
(6) |
| 2022 |
Jan
(5) |
Feb
(4) |
Mar
(8) |
Apr
(6) |
May
(5) |
Jun
(5) |
Jul
(10) |
Aug
(6) |
Sep
(7) |
Oct
(4) |
Nov
(4) |
Dec
(6) |
| 2023 |
Jan
(5) |
Feb
(5) |
Mar
(6) |
Apr
(4) |
May
(5) |
Jun
(6) |
Jul
(5) |
Aug
(5) |
Sep
(5) |
Oct
(5) |
Nov
(7) |
Dec
(8) |
| 2024 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <fwi...@gm...> - 2015-04-29 17:10:43
|
Jim just pointed out that I goofed my links up, so the proper releases are: Installer: https://oss.sonatype.org/content/repositories/orgpython-1051/org/python/jython-installer/2.7.0/jython-installer-2.7.0.jar Standalone: https://oss.sonatype.org/content/repositories/orgpython-1052/org/python/jython-standalone/2.7.0/jython-standalone-2.7.0.jar On Tue, Apr 28, 2015 at 8:15 PM, fwi...@gm... <fwi...@gm...> wrote: > OK all, we're on to the real thing, this could be the real 2.7.0! > Please test, especially if you can test on windows! > > The releases: > > Installer: https://oss.sonatype.org/content/repositories/orgpython-1053/org/python/jython/2.7.0/jython-2.7.0.jar > > Standalone: https://oss.sonatype.org/content/repositories/orgpython-1051/org/python/jython-installer/2.7.0/jython-installer-2.7.0.jar > > The parent directories of each of the above have the checksums, source > jars, javadocs, etc. > > -Frank |
|
From: <fwi...@gm...> - 2015-04-29 03:16:06
|
OK all, we're on to the real thing, this could be the real 2.7.0! Please test, especially if you can test on windows! The releases: Installer: https://oss.sonatype.org/content/repositories/orgpython-1053/org/python/jython/2.7.0/jython-2.7.0.jar Standalone: https://oss.sonatype.org/content/repositories/orgpython-1051/org/python/jython-installer/2.7.0/jython-installer-2.7.0.jar The parent directories of each of the above have the checksums, source jars, javadocs, etc. -Frank |
|
From: Jim B. <jim...@py...> - 2015-04-25 04:12:28
|
So far the reception to RC3 has been good so far, as tracked on http://bugs.jython.org/ (no blocking bugs yet), IRC on #jython, and on the jython-dev/jython-users email lists (I assume no news is good news in this case), and Twitter. Therefore I would like to propose the following: - Soft release of final on *Tuesday April 28*. We want to do a soft release so that we can ensure all tags, NEWS, README, and build.xml are adjusted without incident. - Hard release of final on *Wednesday April 29*. Yay! About time. Of course we will delay and do a RC4 if anything blocking does come up before then. Otherwise, we can start on 2.7.1 and continue work on 3.x. Alex Grönholm in particular has been making great progress on this. I'm thinking about finally supporting invokedynamic for real, including how we can select callsites to be rewritten, and any supporting statistics. And I'm sure others have other interesting plans as well. Fun stuff! - Jim |
|
From: Jython t. <st...@bu...> - 2015-04-24 16:10:21
|
ACTIVITY SUMMARY (2015-04-17 - 2015-04-24) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 242 ( -2) closed 2116 (+11) total 2358 ( +9) Open issues with patches: 31 Issues opened (6) ================= #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 opened by Arfrever #2333: ensurepip passwd.pw_passwd unimplemented http://bugs.jython.org/issue2333 opened by baztian #2336: NullPointerException in gc.collect http://bugs.jython.org/issue2336 opened by jmadden #2337: StackOverflowError in gc.collect http://bugs.jython.org/issue2337 opened by jmadden #2338: readline.py startup hook http://bugs.jython.org/issue2338 opened by eaaltonen #2339: JSR223: NullPointerException in Eclipse following wiki instruc http://bugs.jython.org/issue2339 opened by eaaltonen Most recent 15 issues with no replies (15) ========================================== #2339: JSR223: NullPointerException in Eclipse following wiki instruc http://bugs.jython.org/issue2339 #2331: "java.lang.IllegalArgumentException: Cannot create PyString wi http://bugs.jython.org/issue2331 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2328: RuntimeError: threading.Lock cannot be released by threads oth http://bugs.jython.org/issue2328 #2323: Calling object.__reduce__ in a subclass results in infinite re http://bugs.jython.org/issue2323 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2090: python type 'long' doesn't work well under JSR 223 http://bugs.jython.org/issue2090 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1795: Extending Thread and a java class/interface doesn't work http://bugs.jython.org/issue1795 Top 10 most discussed issues (5) ================================ #2337: StackOverflowError in gc.collect http://bugs.jython.org/issue2337 9 msgs #2336: NullPointerException in gc.collect http://bugs.jython.org/issue2336 7 msgs #1815: http://www.jython.org/license.html should mention the other li http://bugs.jython.org/issue1815 4 msgs #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 3 msgs #2333: ensurepip passwd.pw_passwd unimplemented http://bugs.jython.org/issue2333 3 msgs Issues closed (7) ================= #1031: PyDictionaryDerived.__cmp__ is not fully CPython-compatible http://bugs.jython.org/issue1031 closed by zyasoft #1572: sys-package-mgr should not print import action unless verbose http://bugs.jython.org/issue1572 closed by jeff.allen #1986: __file__ and hasattr are slow for java packages http://bugs.jython.org/issue1986 closed by zyasoft #2327: ImportTests JUnit test fails http://bugs.jython.org/issue2327 closed by jeff.allen #2332: jython -m regrtest failing to find tests http://bugs.jython.org/issue2332 closed by jeff.allen #2334: Jython 2.7rc2 installer doesn't create bash launch script http://bugs.jython.org/issue2334 closed by zyasoft #2335: ImportError: No module named _socket http://bugs.jython.org/issue2335 closed by zyasoft |
|
From: Rory O'D. <ror...@or...> - 2015-04-24 08:08:50
|
Hi Alan/Jim, Early Access build for JDK 9 b60 <https://jdk9.java.net/download/> available on java.net, summary of changes are listed here <http://www.java.net/download/jdk9/changes/jdk9-b60.html> Early Access build for JDK 8u60 b12 <http://jdk8.java.net/download.html> is available on java.net, summary of changes are listed here. <http://www.java.net/download/jdk8u60/changes/jdk8u60-b12.html> Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland |
|
From: Jim B. <jim...@py...> - 2015-04-23 14:49:35
|
One last thing: *we need to freeze https://hg.python.org/jython <https://hg.python.org/jython>* in preparation of the final release. This will help avoid unnecessary headaches as we do release labeling and final README and other text file adjustments. So far everything is looking good, with no new bugs reported and positive feedback on #jython. Perhaps the biggest new risk at this time is the new Jython launch script, which is installed as both the native executable on Windows (so bin/jython.exe) and on non Windows (bin/jython). This new launch script is written in Python itself, a language most of us happen to know quite well ;), and it uses CPython 2.7. On Windows it is converted to an exe with PyInstaller in advance in a manual process and checked in on any change, similar to how we need to run gderived.py or other steps. On other platforms, the installer locates the CPython 2.7 using `/usr/bin/env python2.7 -E`; if this fails, the old and somewhat buggy bash-based launcher script is used instead. One change that I made for RC3 is that the launch script now has its shebang line generated to be the absolute path reported as sys.executable by the CPython 2.7. Two related things came out of this: due to how shebangs are interpreted on different platforms, this fixed an issue that trigoman on #jython was seeing about arg list too long; and it also means that we can also use -E on the launch script. What does this mean? Just that we should test at much as possible, especially on platforms like AIX, HPUX, and Solaris, as well as other platforms like AS/400. The usual advice in other words! :) - Jim On Wed, Apr 22, 2015 at 9:47 AM, fwi...@gm... < fwi...@gm...> wrote: > On behalf of the Jython development team, I'm pleased to announce that > the third release candidate of Jython 2.7 is available. > > Thanks to Amobee for sponsoring my work on Jython, and thanks to the > many contributors to Jython! > > Details are here: > > http://fwierzbicki.blogspot.com/2015/04/jython-27-release-candidate-3-available.html > > -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 |
|
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 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: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: <fwi...@gm...> - 2015-04-22 15:47:30
|
On behalf of the Jython development team, I'm pleased to announce that the third release candidate of Jython 2.7 is available. Thanks to Amobee for sponsoring my work on Jython, and thanks to the many contributors to Jython! Details are here: http://fwierzbicki.blogspot.com/2015/04/jython-27-release-candidate-3-available.html -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-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: 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: 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: <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: Jython t. <st...@bu...> - 2015-04-17 16:10:20
|
ACTIVITY SUMMARY (2015-04-10 - 2015-04-17) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 244 ( +2) closed 2105 ( +8) total 2349 (+10) Open issues with patches: 32 Issues opened (7) ================= #2321: Py.setSystemState() is a no-op http://bugs.jython.org/issue2321 opened by kevinmcmurtrie #2323: Calling object.__reduce__ in a subclass results in infinite re http://bugs.jython.org/issue2323 opened by jmadden #2324: StringIndexOutOfBoundsException using cStringIO.StringIO http://bugs.jython.org/issue2324 opened by jmadden #2327: ImportTests JUnit test fails http://bugs.jython.org/issue2327 opened by jeff.allen #2328: RuntimeError: threading.Lock cannot be released by threads oth http://bugs.jython.org/issue2328 opened by jmadden #2329: Cannot create virtualenv with jython2.7rc2 - breaks tox http://bugs.jython.org/issue2329 opened by csojinb #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 opened by kprussing Most recent 15 issues with no replies (15) ========================================== #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2319: CLASSPATH ignored by new launcher http://bugs.jython.org/issue2319 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #2330: full-build fails to copy CPython License http://bugs.jython.org/issue2330 #2328: RuntimeError: threading.Lock cannot be released by threads oth http://bugs.jython.org/issue2328 #2323: Calling object.__reduce__ in a subclass results in infinite re http://bugs.jython.org/issue2323 #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2090: python type 'long' doesn't work well under JSR 223 http://bugs.jython.org/issue2090 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1795: Extending Thread and a java class/interface doesn't work http://bugs.jython.org/issue1795 Top 10 most discussed issues (7) ================================ #2328: RuntimeError: threading.Lock cannot be released by threads oth http://bugs.jython.org/issue2328 12 msgs #2307: test_chdir failures on Windows http://bugs.jython.org/issue2307 7 msgs #2321: Py.setSystemState() is a no-op http://bugs.jython.org/issue2321 7 msgs #2320: fileno() is -1 on Windows http://bugs.jython.org/issue2320 6 msgs #2324: StringIndexOutOfBoundsException using cStringIO.StringIO http://bugs.jython.org/issue2324 6 msgs #2323: Calling object.__reduce__ in a subclass results in infinite re http://bugs.jython.org/issue2323 5 msgs #2329: Cannot create virtualenv with jython2.7rc2 - breaks tox http://bugs.jython.org/issue2329 5 msgs Issues closed (7) ================= #1540: Calling a Java method from a Python subclass via super() cause http://bugs.jython.org/issue1540 closed by zyasoft #1670: Implicit Decimal conversion to float fails http://bugs.jython.org/issue1670 closed by alex.gronholm #1992: Printing UTF-8 string from Java to Python using PythonInterpre http://bugs.jython.org/issue1992 closed by zyasoft #2171: jython returns NotImplemented for int.__pow__(x,y,None) http://bugs.jython.org/issue2171 closed by alex.gronholm #2322: CVE-2013-1752 - multiple unbound readline() DoS flaws in pytho http://bugs.jython.org/issue2322 closed by alex.gronholm #2325: Piping input to Jython does not suppress printing sys.ps1; bre http://bugs.jython.org/issue2325 closed by zyasoft #2326: RuntimeError: WeakValueDictionary.valuerefs should not use sel http://bugs.jython.org/issue2326 closed by zyasoft |
|
From: Alan K. <jyt...@xh...> - 2015-04-16 09:55:10
|
Hi all, Seeing the enormous pain that cpython is going through with the 2 vs. 3 debate, and getting people to move to 3, I wonder if there anything that jython can do in advance to help prevent some of this pain. For example, maybe jython 2.x executables and links should be named "jython2" explicitly, to prevent the kind of confusion and disagreement that is currently going on in the "what does the /usr/bin/python link point to?" debate. When jython 3.x becomes available, it could be explicitly called "jython3". A little forethought now might save a lot of pain down the road. Just a thought. Alan. |
|
From: Jython t. <st...@bu...> - 2015-04-10 16:10:20
|
ACTIVITY SUMMARY (2015-04-03 - 2015-04-10) Jython tracker at http://bugs.jython.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 242 ( +5) closed 2097 ( +9) total 2339 (+14) Open issues with patches: 30 Issues opened (14) ================== #2307: test_chdir failures on Windows http://bugs.jython.org/issue2307 opened by jeff.allen #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 opened by jeff.allen #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 opened by jeff.allen #2310: test_import failure on Windows http://bugs.jython.org/issue2310 opened by jeff.allen #2311: Remove test_bat_jy and add something like test_jython_launcher http://bugs.jython.org/issue2311 opened by jeff.allen #2312: Test failures related to encoding in a subprocess on Windows http://bugs.jython.org/issue2312 opened by jeff.allen #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 opened by jeff.allen #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 opened by jeff.allen #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 opened by jeff.allen #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 opened by jeff.allen #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 opened by jeff.allen #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 opened by jeff.allen #2319: CLASSPATH ignored by new launcher http://bugs.jython.org/issue2319 opened by zyasoft #2320: fileno() is -1 on Windows http://bugs.jython.org/issue2320 opened by jeff.allen Most recent 15 issues with no replies (15) ========================================== #2320: fileno() is -1 on Windows http://bugs.jython.org/issue2320 #2319: CLASSPATH ignored by new launcher http://bugs.jython.org/issue2319 #2318: test_zipimport_jy failure on Windows http://bugs.jython.org/issue2318 #2317: test_urllib2 failure on Windows http://bugs.jython.org/issue2317 #2316: test_tarfile file-mode failures on Windows http://bugs.jython.org/issue2316 #2315: test_ssl failure on Windows http://bugs.jython.org/issue2315 #2314: test_shutil failures on Windows http://bugs.jython.org/issue2314 #2313: test_jython_initializer failure on Windows http://bugs.jython.org/issue2313 #2309: test_classpathimporter fails on Windows. http://bugs.jython.org/issue2309 #2308: test___all__ fails at modjy http://bugs.jython.org/issue2308 #2295: Importation of modules with str names with non-ASCII character http://bugs.jython.org/issue2295 #2294: Importation of modules from directories with non-ASCII charact http://bugs.jython.org/issue2294 #2293: "java.lang.IllegalArgumentException: java.lang.IllegalArgument http://bugs.jython.org/issue2293 #2286: 'IllegalArgumentException: java.lang.IllegalArgumentException: http://bugs.jython.org/issue2286 #2278: Jython runtime instrumentation http://bugs.jython.org/issue2278 Most recent 15 issues waiting for review (15) ============================================= #2230: Jython evaluation blocks under heavy load with high multi-core http://bugs.jython.org/issue2230 #2228: [PATCH] Re-use "makeCompiledFilename" function where possible http://bugs.jython.org/issue2228 #2171: jython returns NotImplemented for int.__pow__(x,y,None) http://bugs.jython.org/issue2171 #2143: site-packages support in standalone jar http://bugs.jython.org/issue2143 #2142: Set Thread classloader when entering Jython context http://bugs.jython.org/issue2142 #2090: python type 'long' doesn't work well under JSR 223 http://bugs.jython.org/issue2090 #2077: marshal doesn't raise error when fed unmarshalable object http://bugs.jython.org/issue2077 #1925: Support loading java.sql.Drivers that aren't on the boot class http://bugs.jython.org/issue1925 #1917: No ctypes.c_char http://bugs.jython.org/issue1917 #1866: Parser does not have mismatch token error messages caught by B http://bugs.jython.org/issue1866 #1842: Add IBM i support to Jython http://bugs.jython.org/issue1842 #1796: Jython doesn't support jar dir with colon's in it http://bugs.jython.org/issue1796 #1795: Extending Thread and a java class/interface doesn't work http://bugs.jython.org/issue1795 #1767: Rich comparisons http://bugs.jython.org/issue1767 #1741: com.ziclix.python.sql.DataHandler calls wasNull without previo http://bugs.jython.org/issue1741 Top 10 most discussed issues (1) ================================ #2307: test_chdir failures on Windows http://bugs.jython.org/issue2307 3 msgs Issues closed (5) ================= #1000: JFileChooser java bug in installer http://bugs.jython.org/issue1000 closed by zyasoft #1978: Jython launcher shell script fails on OS/X 10.8 (Mountain Lion http://bugs.jython.org/issue1978 closed by zyasoft #2246: Windows regrtest failures http://bugs.jython.org/issue2246 closed by zyasoft #2303: Some time methods lack don't have set the __module__ attributt http://bugs.jython.org/issue2303 closed by alex.gronholm #2304: operator members lack a __module__ attribute correctly set http://bugs.jython.org/issue2304 closed by alex.gronholm |
|
From: Jim B. <jim...@py...> - 2015-04-10 03:32:21
|
We have had one bug report so far that will require a release candidate 3, http://bugs.jython.org/issue2319 - CLASSPATH ignored by new launcher The workaround is simple: use the -classpath option for the Jython launcher. So this means: bin/jython -classpath=$CLASSPATH ... or on Windows bin/jython.exe -classpath=%CLASSPATH% ... (You can also add these jars to your JYTHONPATH.) We will have this issue fixed early in next week's PyCon sprints along with additional unit tests on launcher options (http://bugs.jython.org/issue2311 ) On Thu, Apr 9, 2015 at 1:27 AM, fwi...@gm... <fwi...@gm... > wrote: > On behalf of the Jython development team, I'm pleased to announce that > the second release candidate of Jython 2.7 is available. The windows > installer issues from rc1 should now be fixed. > > Thanks to Amobee for sponsoring my work on Jython, and thanks to the > many contributors to Jython! > > Details are here: > > http://fwierzbicki.blogspot.com/2015/04/jython-27-release-candidate-2-available.html > > -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 > -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
|
From: <fwi...@gm...> - 2015-04-09 05:27:35
|
On behalf of the Jython development team, I'm pleased to announce that the second release candidate of Jython 2.7 is available. The windows installer issues from rc1 should now be fixed. Thanks to Amobee for sponsoring my work on Jython, and thanks to the many contributors to Jython! Details are here: http://fwierzbicki.blogspot.com/2015/04/jython-27-release-candidate-2-available.html -Frank |
|
From: Jeff A. <ja...@fa...> - 2015-04-06 21:23:58
|
I've done nothing but complain all evening: issues 2307-2317. That covers all the rc2 failures detected here. Jeff Allen On 06/04/2015 15:57, Jim Baker wrote: > Jeff, > > On Mon, Apr 6, 2015 at 8:50 AM, Jeff Allen <ja...@fa... > <mailto:ja...@fa...>> wrote: > > OK. I'll open issues for other non-flaky tests failing on Windows, > when I reach a pause in chdir, where no-one beats me to it. I may > shuffle things between lists in regrtest, but a skip conditioned > on windows & jython seems better in retrospect. > > > Sounds like a good plan. > |
|
From: Jim B. <jim...@py...> - 2015-04-06 15:02:20
|
Oops, forgot to reply-all. Since I wrote this last email, the issue reported by Roland Walter has been resolved. The fix - ensuring JYTHON_HOME is not pointing to an old release and not having the old Jython on PATH - should be documented in the release notes, since that will likely trip other people once they try to upgrade to 2.7 from 2.5. - Jim ---------- Forwarded message ---------- From: Jim Baker <jim...@py...> Date: Mon, Apr 6, 2015 at 8:13 AM Subject: Re: [Jython-dev] Jython 2.7 rc2 soft launch To: Jeff Allen <ja...@fa...> On Sun, Apr 5, 2015 at 9:30 AM, Jeff Allen <ja...@fa...> wrote: > It installed ok on Windows 7 64-bit, from jython-installer-2.7-rc2, > running with Java 1.8.0_40. > > Running regrtest -e (this time on Java 1.7.0_60), I get 22 failures. Not > to detract from the hard work over the last 4 months or so, which has > been great, the result feels a little rough for a release candidate. How > is it on Linux (sorry, my KVM is playing up) and Mac? > Although occasionally flaky, most of the time we get 100% tests passing on Ubuntu 14.10 and OX 10.10.2. Flakiness is seen on those platforms in test_jython_initializer, test_socket and other networking tests, test_tarfile. At this point, it seems to be mostly due to a problem in the tests than what is being tested. I would like to have converged to zero failures for Windows, but this feels like probably a few more months of work at least. At this point, the release candidate seems to be solid, but we did have one report from Roland Walter that the jython.exe launcher is failing on Windows: http://bugs.jython.org/msg9755 (http://bugs.jython.org/issue2297) when it attempts to launch java itself in a subprocess. To be further investigated. > Is 22 failures within expectations/comfort? Yes, and working to either fix the underlying failure; fix the test itself; or remove it entirely. Hopefully we can make good progress on this for 2.7.1 > Shouldn't all failures at > least be "expected" failures at this stage, with a bug report tracking > them? > That's a good idea - we should open up a bug per test, or at least group of tests. It would be a good way to kick off 2.7.1 dev work as well. > My bottom line is: > > 354 tests OK. > > 13 tests skipped: > > test__osx_support test_commands test_curses test_dbm test_lib2to3 > > test_pickle test_pipes test_sax test_smtpnet test_socketserver > > test_subprocess test_urllib2net test_urllibnet > > 7 skips unexpected: > > test__osx_support test_commands test_dbm test_lib2to3 test_pickle > > test_pipes test_sax > > 22 tests failed: > > test___all__ test_bat_jy test_chdir test_classpathimporter > > test_file2k test_httpservers test_import test_inspect > > test_jython_initializer test_netrc test_py_compile test_runpy > > test_select test_shutil test_socket test_ssl test_sys test_sys_jy > > test_tarfile test_urllib2 test_zipfile test_zipimport_jy > > 22 fails unexpected: > > test___all__ test_bat_jy test_chdir test_classpathimporter > > test_file2k test_httpservers test_import test_inspect > > test_jython_initializer test_netrc test_py_compile test_runpy > > test_select test_shutil test_socket test_ssl test_sys test_sys_jy > > test_tarfile test_urllib2 test_zipfile test_zipimport_jy > > > Of these, the following 19 are hard failures (repeatable at the prompt > with jython -m ...): > test___all__ > test_bat_jy (passé, but is there a test_exe_jy to take its place?) > I should have removed test_bat_jy from testing. The test itself should be renamed to something like test_jython_launcher and then tested for both jython.py and jython.exe, given that it seems reasonable. > test_chdir > Should be fixed, per your comments on http://bugs.jython.org/issue2307 test_classpathimporter > test_file2k > test_httpservers (may be security s/w interference) > test_import > test_jython_initializer > Flaky test > test_netrc > test_py_compile > test_runpy (repeatable, but an unlink() error suggesting poor hygiene) > test_shutil > test_ssl > Flaky > test_sys > test_sys_jy > test_tarfile (some unlink(), some file mode) > test_urllib2 > test_zipfile (all unlink()) > test_zipimport_jy > --- > > test_inspect fails in test_findsource_binary under regrtest, which is > skipped when it runs at the prompt. Odd. > Agreed about that > > test_gc is very noisy ("gc: The PyObject-subclass blah-blah should > either implement Traverseproc or ...") but doesn't actually fail. > This is new with Stefan's work on supporting visibility of gc. I expect to see this to get quieter. > > You are skipping test_subprocess, but that actually passes for me on > Windows (takes 10 minutes to run, tho'.) > Running test_subprocess requires enabling the subprocess resource with --use. This is enabled by default with ant regrtest (or ant test). -- - Jim jim.baker@{colorado.edu|python.org|rackspace.com|zyasoft.com} twitter.com/jimbaker github.com/jimbaker bitbucket.com/jimbaker |
|
From: Jim B. <jim...@py...> - 2015-04-06 14:58:18
|
Jeff, On Mon, Apr 6, 2015 at 8:50 AM, Jeff Allen <ja...@fa...> wrote: > OK. I'll open issues for other non-flaky tests failing on Windows, when I > reach a pause in chdir, where no-one beats me to it. I may shuffle things > between lists in regrtest, but a skip conditioned on windows & jython seems > better in retrospect. > Sounds like a good plan. > > I hadn't noticed the difference between ant regrtest and calling with -m. > On that subject, since the new launcher (I think), I see: > >dist\bin\jython -m test.regrtest -e > test_grammar > test_opcodes > ... > All 9 tests OK. > :( > > Whereas > >dist\bin\jython Lib\test\regrtest.py -e > runs all the tests I expect. > > Any ideas? It is as if regrtest does not find the test directory to > enumerate it. > Yes, that sounds about right. Not certain what is going on here, but it's more or less a problem confined in the regrtest module itself, since jython.exe is used in both cases. Most importantly, does not look like a show stopper! - Jim |
|
From: Jeff A. <ja...@fa...> - 2015-04-05 15:44:17
|
It installed ok on Windows 7 64-bit, from jython-installer-2.7-rc2,
running with Java 1.8.0_40.
Running regrtest -e (this time on Java 1.7.0_60), I get 22 failures. Not
to detract from the hard work over the last 4 months or so, which has
been great, the result feels a little rough for a release candidate. How
is it on Linux (sorry, my KVM is playing up) and Mac?
Is 22 failures within expectations/comfort? Shouldn't all failures at
least be "expected" failures at this stage, with a bug report tracking them?
My bottom line is:
354 tests OK.
13 tests skipped:
test__osx_support test_commands test_curses test_dbm test_lib2to3
test_pickle test_pipes test_sax test_smtpnet test_socketserver
test_subprocess test_urllib2net test_urllibnet
7 skips unexpected:
test__osx_support test_commands test_dbm test_lib2to3 test_pickle
test_pipes test_sax
22 tests failed:
test___all__ test_bat_jy test_chdir test_classpathimporter
test_file2k test_httpservers test_import test_inspect
test_jython_initializer test_netrc test_py_compile test_runpy
test_select test_shutil test_socket test_ssl test_sys test_sys_jy
test_tarfile test_urllib2 test_zipfile test_zipimport_jy
22 fails unexpected:
test___all__ test_bat_jy test_chdir test_classpathimporter
test_file2k test_httpservers test_import test_inspect
test_jython_initializer test_netrc test_py_compile test_runpy
test_select test_shutil test_socket test_ssl test_sys test_sys_jy
test_tarfile test_urllib2 test_zipfile test_zipimport_jy
Of these, the following 19 are hard failures (repeatable at the prompt
with jython -m ...):
test___all__
test_bat_jy (passé, but is there a test_exe_jy to take its place?)
test_chdir
test_classpathimporter
test_file2k
test_httpservers (may be security s/w interference)
test_import
test_jython_initializer
test_netrc
test_py_compile
test_runpy (repeatable, but an unlink() error suggesting poor hygiene)
test_shutil
test_ssl
test_sys
test_sys_jy
test_tarfile (some unlink(), some file mode)
test_urllib2
test_zipfile (all unlink())
test_zipimport_jy
---
test_inspect fails in test_findsource_binary under regrtest, which is
skipped when it runs at the prompt. Odd.
test_gc is very noisy ("gc: The PyObject-subclass blah-blah should
either implement Traverseproc or ...") but doesn't actually fail.
You are skipping test_subprocess, but that actually passes for me on
Windows (takes 10 minutes to run, tho'.)
Jeff Allen
On 04/04/2015 19:54, fwi...@gm... wrote:
> Please test, specially if you can test on windows!
>
> The releases:
>
> Installer: https://oss.sonatype.org/content/repositories/orgpython-1045/org/python/jython-installer/2.7-rc2/jython-installer-2.7-rc2.jar
>
> Standalone: https://oss.sonatype.org/content/repositories/orgpython-1046/org/python/jython-standalone/2.7-rc2/jython-standalone-2.7-rc2.jar
>
> The parent directories of each of the above have the checksums, source
> jars, javadocs, etc.
>
> -Frank
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>
|
101 messages has been excluded from this view by a project administrator.
