Running tests on freebsd5
Hi, I just checked out the Python CVS head, ran configure and compiled succesfully on FreeBSD 5.0. I then ran 'make tests', and had two failing tests. I don't think these errors are related to FreeBSD5.0, so I post them here. Can somebody add the lists of tests for 'freebsd5' to regrtest.py, and have a look at these tracebacks? PieterB -- http://zwiki.org/PieterB ... 2 tests failed: test_socket test_tempfile 34 tests skipped: test_aepack test_al test_bsddb test_bsddb185 test_bsddb3 test_cd test_cl test_curses test_dbm test_email_codecs test_fcntl test_gdbm test_gl test_imgfile test_ioctl test_linuxaudiodev test_locale test_macfs test_macostools test_mpz test_nis test_normalization test_ossaudiodev test_pep277 test_plistlib test_scriptpackages test_socket_ssl test_socketserver test_sunaudiodev test_timeout test_unicode_file test_urllibnet test_winreg test_winsound Ask someone to teach regrtest.py about which tests are expected to get skipped on freebsd5. ------------------------------------------------------------------ When running test_socket.py, I get the following traceback: Ran 51 tests in 2.470s FAILED (errors=1) Traceback (most recent call last): File "test_socket.py", line 755, in ? test_main() File "test_socket.py", line 752, in test_main test_support.run_unittest(*tests) File ".../src/Lib/test/test_support.py", line 259, in run_unittest run_suite(suite, testclass) File ".../src/Lib/test/test_support.py", line 247, in run_suite raise TestFailed(err) test.test_support.TestFailed: Traceback (most recent call last): File "test_socket.py", line 215, in testCrucialConstants socket.SOCK_RDM AttributeError: 'module' object has no attribute 'SOCK_RDM' ----------------------------------------------------------------- When I run test_tempfile.py I get: Ran 34 tests in 0.703s FAILED (failures=1) Traceback (most recent call last): File "test_tempfile.py", line 651, in ? test_main() File "test_tempfile.py", line 648, in test_main test_support.run_unittest(*test_classes) File ".../src/Lib/test/test_support.py", line 259, in run_unittest run_suite(suite, testclass) File ".../src/Lib/test/test_support.py", line 247, in run_suite raise TestFailed(err) test.test_support.TestFailed: Traceback (most recent call last): File "test_tempfile.py", line 299, in test_noinherit self.failIf(retval > 0, "child process reports failure") File ".../src/Lib/unittest.py", line 264, in failIf if expr: raise self.failureException, msg AssertionError: child process reports failure
PieterB <pieterb@gewis.nl> writes:
AttributeError: 'module' object has no attribute 'SOCK_RDM'
It appears your system either does not support SOCK_RDM, or somehow Python failed to pickup the definition of SOCK_RDM. An expert for your system would have to determine which one it is. He would then need to investigate whether not providing this constant is a deliberate omission, a known bug, or an unknown bug. If it is a known or unknown bug, the test deserves to fail - Python tests often fail because of bugs in the system. If this is a deliberate omission, somebody should give us the rationale for this omission, so we can reconsider not to treat SOCK_RDM as a crucial constant.
AssertionError: child process reports failure
You will have to find out in more detail why this happens. Find out what sys.executable, tester, v, and d are, then find out whether the process is invoked correctly. If it is not invoked, find out why. If it is invoked, find out whether it returns 1, or some other value. If it returns some other value, find out which value and why. If it returns 1, find out which of the two sys.exits in tf_inherit_check.py is taken. And so on. Regards, Martin
On Sun, 29 Jun 2003, PieterB wrote:
2 tests failed: test_socket test_tempfile
I'm aware of these 2, and there are some other niggling issues with FreeBSD 5.x that I've been looking at. Some of these issues won't stabilise until the FreeBSD team choose to declare 5.x a "stable" branch. 5.0 in particular is not a good release to target for solid support. There are a couple of issues on FreeBSD 4.x that need attention too, and as 4.x is still the official stable release, these will likely get my priority. BTW, a bug report on SF is a more appropriate place for a report like this. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac@pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia
On Sun, Jun 29, 2003 at 02:01:07PM +0200, PieterB wrote:
Hi,
I just checked out the Python CVS head, ran configure and compiled succesfully on FreeBSD 5.0. I then ran 'make tests', and had two failing tests. I don't think these errors are related to FreeBSD5.0, so I post them here.
Unfortunately, at least one of them is: $man socket says "... The types SOCK_RAW, which is available only to the super-user, and SOCK_RDM, which is planned, but not yet implemented, are not described here. ..."
When running test_socket.py, I get the following traceback: Ran 51 tests in 2.470s
...
File "test_socket.py", line 215, in testCrucialConstants socket.SOCK_RDM AttributeError: 'module' object has no attribute 'SOCK_RDM'
- Till
participants (4)
-
Andrew MacIntyre -
martin＠v.loewis.de -
PieterB -
Till Plewe