Issue 814976: test_types fails on HP/UX ia64 (original) (raw)

Created on 2003-09-30 08:51 by anthonybaxter, last changed 2022-04-10 16:11 by admin. This issue is now closed.

Messages (6)
msg18450 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-09-30 08:51
6. Built-in types 6.1 Truth value testing 6.2 Boolean operations 6.3 Comparisons 6.4 Numeric types (mostly conversions) 6.4.1 32-bit integers 6.4.2 Long integers 6.4.3 Floating point numbers 6.5 Sequence types 6.5.1 Strings 6.5.2 Tuples 6.5.3 Lists 6.5.3a Additional list operations Traceback (most recent call last): File "/house/arbatpy/Python-2.3.2c1/Lib/test/test_types.py", line 415, in ? else: raise TestFailed, 'list sort compare function is not callable' test.test_support.TestFailed: list sort compare function is not callable The test in question is definately failing: >>> z=range(12) >>> z.sort(2) >>> (it should raise a TypeError). Anyone?
msg18451 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-09-30 08:52
Logged In: YES user_id=29957 wow. I exited python after the above z = range(12) z.sort(2) and got Exception exceptions.TypeError: "'int' object is not callable" in 'garbage collection' ignored Fatal Python error: unexpected exception during garbage collection ABORT instruction (core dumped)
msg18452 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-09-30 08:53
Logged In: YES user_id=29957 Python 2.3.2c1 (#2, Sep 30 2003, 04:35:11) [C] on hp-ux11 Type "help", "copyright", "credits" or "license" for more information. >>> import gc >>> z=range(12) >>> z.sort(2) >>> gc.collect() TypeError: 'int' object is not callable >>>
msg18453 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-10-01 07:00
Logged In: YES user_id=29957 Linux/ia64 works fine. Building --without-threads and with gcc on HPUX/ia64 passes test_types, but fails with some dynamic linking errors (__divdf3) in test_audioop. Looks like the bug is in the HP/UX compiler.
msg18454 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-10-01 07:14
Logged In: YES user_id=29957 I've sent in a note to the feedback address on the HP site - I don't know if they're likely to respond or not. Ok, I blew everything away and started again with absolutely 100% no optimisation involved, and this time it worked!?! I was trying it on the "other" HP/ia64 box (there's two in the testdrive farm).
msg18455 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2003-10-01 08:53
Logged In: YES user_id=29957 Closing this now - it's a bug in the HP compiler. I've put a workaround in the HP/UX section of the toplevel README file.
History
Date User Action Args
2022-04-10 16:11:29 admin set github: 39336
2003-09-30 08:51:10 anthonybaxter create