[lxml-dev] trunk test problems, release tags

[jholg at gmx.de]

Hi,

I'm having issues with the latest trunk head. When trying to test my build it suddenly just hangs, and has then to get killed the hard way:

0 lb54320 at adevp02 .../trunk $ python2.4 test.py -p -v
/data/pydev/hjoukl/LXML/tmp/trunk/src/lxml/html/__init__.py:22: UserWarning: This version of libxml2 has a known XPath bug. Use it at your own risk.
  _rel_links_xpath = etree.XPath("descendant-or-self::a[@rel]")
 
TESTED VERSION: 2.0.alpha4-47483
    Python:            (2, 4, 4, 'final', 0)
    lxml.etree:        (2, 0, -196, 47483)
    libxml used:       (2, 6, 27)
    libxml compiled:   (2, 6, 27)
    libxslt used:      (1, 1, 20)
    libxslt compiled:  (1, 1, 20)
 
 172/824 ( 20.9%): test_element_with_attributes_ns (lxml.tests.test_elementtree.ETreeTestCase) ^Z[1]+  Stopped                 python2.4 test.py -p -v
0 lb54320 at adevp02 .../trunk $ kill -9 %+

I've tried this with newer libxml2/libxslt versions and it shows just the same behaviour. It is also reproducible on different (solaris) machines.
I'm building with the latest Cython 0.9.6.7 on sparc Solaris.

Testing an 1.3.3 checkout works just fine, on the same machine, with the same library versions.

Trussing the test run doesn't really tell me much:

0 lb54320 at adevp02 .../trunk $ truss python2.4 test.py -p -vv    
[...]
test_element_with_attributes_keywords (lxml.tests.test_elementtree.ETreeTestCase)write(2, " t e s t _ e l e m e n t".., 81)     = 81
 ... write(2, "   . . .  ", 5)                  = 5
mkdir("/tmp/tmpV5TpiJ", 0700)                   = 0
open64("/tmp/tmpV5TpiJ", O_RDONLY|O_NDELAY)     = 3
fcntl(3, F_SETFD, 0x00000001)                   = 0
fstat64(3, 0xFFBED3E8)                          = 0
getdents64(3, 0x007CD178, 1048)                 = 48
getdents64(3, 0x007CD178, 1048)                 = 0
close(3)                                        = 0
rmdir("/tmp/tmpV5TpiJ")                         = 0
okwrite(2, " o k", 2)                           = 2
 
write(2, "\n", 1)                               = 1
 172write(2, "\r   1 7 2", 5)                   = 5
/824 ( 20.9%)write(2, " / 8 2 4   (   2 0 . 9 %".., 13) = 13
: write(2, " :  ", 2)                           = 2
test_element_with_attributes_ns (lxml.tests.test_elementtree.ETreeTestCase)write(2, " t e s t _ e l e m e n t".., 75)   = 75
 ... write(2, "   . . .  ", 5)                  = 5
mkdir("/tmp/tmpvCHqNz", 0700)                   = 0
^Z
[1]+  Stopped                 truss python2.4 test.py -p -vv
0 lb54320 at adevp02 .../trunk $ kill -9 %+
 
[1]+  Stopped                 truss python2.4 test.py -p -vv
0 lb54320 at adevp02 .../trunk $

Any hints on what might be going wrong? I didn't see anything like this with my last trunk checkout (that's when I reported a core dump for the empty schematron test case).


To try and investigate further I wanted to check with an earlier 2.0alpha version, but:

0 lb54320 at adevp02 .../lxml-1.3 $ svn list https://codespeak.net/svn/lxml/tag
before-dom-nodereg-removal/
before-grisel-patch/
lxml-0.5/
lxml-0.5.1/
lxml-0.6/
lxml-0.7/
lxml-0.8/
lxml-0.9/
lxml-1.0/
lxml-1.0.1/
lxml-1.0.2/
lxml-1.0.3/
lxml-1.0.4/
lxml-1.0.beta/
lxml-1.1/
lxml-1.1.1/
lxml-1.1.2/
lxml-1.1alpha/
lxml-1.1beta/
lxml-1.2/
lxml-1.2.1/
lxml-1.3/
lxml-1.3.1/
lxml-1.3.2/
lxml-1.3.3/

Not all (development) releases have been tagged, e.g. 1.3.4 and also the complete 2.0alpha line.

Holger




-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger