Rich Burridge wrote:
>
> /net/stard.us.oracle.com/tank/ws/UL/7177355/components/python/python27/test-trans.txt
So the test_multiprocessing failure is new:
test_multiprocessing
Process Process-17:
Traceback (most recent call last):
File ".../Python-2.7.3/Lib/multiprocessing/process.py", line 258, in
_bootstrap
self.run()
File ".../Python-2.7.3/Lib/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
File ".../Python-2.7.3/Lib/test/test_multiprocessing.py", line 1558, in
_writefd
os.dup2(conn.fileno(), i)
OSError: [Errno 9] Bad file number
test test_multiprocessing failed -- Traceback (most recent call last):
File ".../Python-2.7.3/Lib/test/test_multiprocessing.py", line 1613, in
test_large_fd_transfer
self.assertEqual(f.read(), b"bar")
AssertionError: '' != 'bar'
That's a bit disconcerting, but that code is new, so it could just be a
problem with the test, and not with Python.
I'm not happy about the test_sys failure, either, though I suspect that may
have something to do with the dtrace patch.
The other failures simply say you need to run in verbose mode to know what
went wrong. Boo.
Given that there doesn't appear to be a regression here, I wouldn't
consider it a requirement to analyze these failures prior to putback, but
it'd be nice if you could do that, or at least file some bugs (maybe check
to make sure they're not already filed in the python bug tracker).
Thanks,
Danek
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
