Author jeff.allen
Recipients jamesmudd, jeff.allen, stefan.richthofer
Date 2017-03-12.20:18:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My observation of 2.7.1rc1:

    test_java_integration # non-portable use of "/"

cannot be reproduced in my development environment. What I see in test is:
ERROR: test_custom_proxymaker (__main__.SerializationTest)
Traceback (most recent call last):
  File "D:\hg\jython-int\Lib\test\", line 744, in test_custom_proxymaker
    subprocess.check_call(["jar", "cf", proxies_jar_path, "-C", tempdir, "org/"])
  File "C:\Jython\2.7.1rc1\Lib\", line 514, in check_call
    retcode = call(*popenargs, **kwargs)
  File "C:\Jython\2.7.1rc1\Lib\", line 501, in call
    return Popen(*popenargs, **kwargs).wait()
  File "C:\Jython\2.7.1rc1\Lib\", line 856, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "C:\Jython\2.7.1rc1\Lib\", line 1360, in _execute_child
    raise OSError(errno.ENOENT, os.strerror(errno.ENOENT))
OSError: [Errno 2] No such file or directory

However, the OSError seems actually to be because the jar command is not on the path. The test environment only has the JRE. I'll see if I can add a clever skip.
Date User Action Args
2017-03-12 20:18:14jeff.allensetmessageid: <>
2017-03-12 20:18:14jeff.allensetrecipients: + jeff.allen, stefan.richthofer, jamesmudd
2017-03-12 20:18:14jeff.allenlinkissue2554 messages
2017-03-12 20:18:13jeff.allencreate