Source: crmsh
Version: 4.1.0-2
Severity: serious
X-Debbugs-CC: debian-ci@lists.debian.org, lxml@packages.debian.org
Tags: sid bullseye
User: debian-ci@lists.debian.org
Usertags: needs-update
Control: affects -1 src:lxml
Dear maintainers,
With a recent upload of lxml the autopkgtest of crmsh fails in testing
when that autopkgtest is run with the binary packages of lxml from
unstable. It passes when run with only packages from testing. In tabular
form:
pass fail
lxml from testing 4.4.1-1
crmsh from testing 4.1.0-2
versioned deps [0] from testing from unstable
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of lxml to testing
[1]. Of course, lxml shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in lxml was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from lxml should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=lxml
https://ci.debian.net/data/autopkgtest/testing/amd64/c/crmsh/2911559/log.gz
======================================================================
FAIL: test_configs (unittests.test_parse.TestCliParser)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/share/crmsh/tests/unittests/test_parse.py", line 725, in
test_configs
self.assertEqual(expected, result)
AssertionError: '<rsc[65 chars]sion attribute="#uname" operation="eq"
value="[26 chars]ion>' != '<rsc[65 chars]sion operation="eq"
attribute="#uname" value="[26 chars]ion>'
- <rsc_location id="l2" rsc="c"><rule id="l2-rule1"
score="100"><expression attribute="#uname" operation="eq"
value="node1"/></rule></rsc_location>
?
---------------
+ <rsc_location id="l2" rsc="c"><rule id="l2-rule1"
score="100"><expression operation="eq" attribute="#uname"
value="node1"/></rule></rsc_location>
?
+++++++++++++++
-------------------- >> begin captured stdout << ---------------------
ERROR: Reference not found: d1-ops
ERROR: Reference not found: d1
ERROR: Reference not found: l2-rule1
ERROR: Reference not found: l2
--------------------- >> end captured stdout << ----------------------
======================================================================
FAIL: test_fencing (unittests.test_parse.TestCliParser)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/share/crmsh/tests/unittests/test_parse.py", line 460, in
test_fencing
self.assertEqual(expect, xml_tostring(out))
AssertionError: '<fen[24 chars]evel devices="poison-pill" index="1"
target="h[329 chars]ogy>' != '<fen[24 chars]evel target="ha-one"
index="1" devices="poison[329 chars]ogy>'
Diff is 821 characters long. Set self.maxDiff to None to see it.
======================================================================
FAIL: Test node attribute fence target assignment
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/share/crmsh/tests/unittests/test_parse.py", line 477, in
test_fencing_1114
self.assertEqual(expect, xml_tostring(out))
AssertionError: '<fen[24 chars]evel devices="poison-pill" index="1"
target-at[131 chars]ogy>' != '<fen[24 chars]evel index="1"
devices="poison-pill" target-at[131 chars]ogy>'
- <fencing-topology><fencing-level devices="poison-pill" index="1"
target-attribute="rack" target-value="1"/><fencing-level devices="power"
index="2" target-attribute="rack" target-value="1"/></fencing-topology>
+ <fencing-topology><fencing-level index="1" devices="poison-pill"
target-attribute="rack" target-value="1"/><fencing-level index="2"
devices="power" target-attribute="rack"
target-value="1"/></fencing-topology>
----------------------------------------------------------------------
Attachment:
signature.asc
Description: OpenPGP digital signature