[Python-bugs-list] [ python-Bugs-512007 ] make test failure on sunos5

[noreply@sourceforge.net]

Bugs item #512007, was opened at 2002-02-02 04:25
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=512007&group_id=5470

Category: Build
Group: Python 2.2
Status: Open
Resolution: None
Priority: 7
Submitted By: Barry Warsaw (bwarsaw)
Assigned to: Nobody/Anonymous (nobody)
Summary: make test failure on sunos5

Initial Comment:
I don't have time to dig into this right now, but this
shouldn't get lost.  I just tried to build and test
current 2.2+ cvs on a SunOS 5.8 box on the SourceForge
compile farm.  This may be shallow, but here are the
results:

bash-2.03$ uname -a
SunOS usf-cf-sparc-solaris-2 5.8 Generic_108528-11
sun4u sparc SUNW,Ultra-60

[...]

163 tests OK.
4 tests failed:
    test_pwd test_socket test_sundry test_urllib2
20 tests skipped:
    test___all__ test_al test_asynchat test_bsddb
test_cd test_cl
    test_curses test_gdbm test_gl test_imgfile
test_linuxaudiodev
    test_minidom test_openpty test_pyexpat test_sax
test_socket_ssl
    test_socketserver test_sunaudiodev test_winreg
test_winsound
Ask someone to teach regrtest.py about which tests are
expected to get skipped on sunos5.
*** Error code 1
make: Fatal error: Command failed for target `test'


----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2002-03-21 14:40

Message:
Logged In: YES 
user_id=21627

Perhaps Barry could clarify what he thinks the problem is:
that there are failed test cases, that there is no list of
expected-skips on sunos5, or that a specific test case
failed or was skipped (if so, which one)?

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2002-03-21 14:08

Message:
Logged In: YES 
user_id=33168

No, I had 16 skipped tests for 2.2.1.  I think it was about
20 skipped tests for CVS version.  I only meant to point out
that there were no failures.

I used to have _socket failures (I think it was socket
failures) too.  But I thought the problem only occured with
purify.  I have several outstanding patches to get python to
work.  One is documented in #472642.

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2002-03-21 13:27

Message:
Logged In: YES 
user_id=6656

I've seen this trying to build 2.2.1 on the compile farm
machines.

I was hoping to get away with claiming the compile-farm
machines are broken <wink>.

_socket doesn't get built, which is kind of serious.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2002-03-21 12:28

Message:
Logged In: YES 
user_id=21627

Are you saying you have no skipped tests? Not even winsound?

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2002-03-21 03:30

Message:
Logged In: YES 
user_id=33168

Is this still a problem?  2.2.1c1 and 2.3 (CVS) work here 
(170/175 tests OK, no failures):
SunOS rest 5.8 Generic_108528-11 sun4u sparc SUNW,Sun-Blade-100

ie, Solaris 8

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2002-02-02 12:42

Message:
Logged In: YES 
user_id=21627

The "skipped on platform xy" approach is inherently broken.
minidom and pyexpat are not necessarily skipped; they are
only skipped if no expat library was found during build.
Likewise, the gdbm tests are skipped if no gdbm is installed.

Furthermore, "on sunos5" says nearly nothing; Solaris 2.3
classifies as sunos5 just as well as Solaris8, yet Solaris 8
has many more functions built-in.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=512007&group_id=5470