Bug#952200: libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
On Tue, Apr 14, 2020 at 08:25:53PM +0300, Adrian Bunk wrote: > On Sun, Mar 29, 2020 at 10:18:05PM +0200, Andrea Bolognani wrote: > >... > > Adrian, I see you tagged the bug as fixed-upstream: can you please > > share any additional information you might have and that convinced > > you the bug is no longer present upstream? Thanks in advance! > > Sorry for failing to include this information, > please see the commit linked above. Thanks Adrian! I had already tracked down the commit myself in the meantime, and I have prepared an updated libvirt-dbus package that's pending review: https://salsa.debian.org/libvirt-team/libvirt-dbus/-/merge_requests/1 Hopefully we'll be able to upload it soon :) -- Andrea Bolognani Resistance is futile, you will be garbage collected. signature.asc Description: PGP signature
Bug#952200: libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Control: forwarded -1 https://gitlab.com/libvirt/libvirt-dbus/-/commit/9950c0c46d7eb3f3e7052b34464e8499b67d358a On Sun, Mar 29, 2020 at 10:18:05PM +0200, Andrea Bolognani wrote: >... > Adrian, I see you tagged the bug as fixed-upstream: can you please > share any additional information you might have and that convinced > you the bug is no longer present upstream? Thanks in advance! Sorry for failing to include this information, please see the commit linked above. cu Adrian
Bug#952200: libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
On Sun, Feb 23, 2020 at 02:09:46PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > test_connect.py F. > > [100%] > > > > === FAILURES > > === > > ___ TestConnect.test_connect_node_device_create_xml > > > > Fixture "node_device_create" called directly. Fixtures are not meant to be > > called directly, > > but are created automatically when test functions request them as > > parameters. > > See https://docs.pytest.org/en/latest/fixture.html for more information > > about fixtures, and > > https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly > > about how to update your code. > > = 1 failed, 33 passed in 3.89 seconds > > == > > FAIL test_connect.py (exit status: 1) > > The full build log is available from: >http://qa-logs.debian.net/2020/02/22/libvirt-dbus_1.3.0-1_unstable.log Lucas, thanks for the report, and sorry for not noticing it earlier! I'll look into it. Adrian, I see you tagged the bug as fixed-upstream: can you please share any additional information you might have and that convinced you the bug is no longer present upstream? Thanks in advance! -- Andrea Bolognani Resistance is futile, you will be garbage collected. signature.asc Description: PGP signature
Bug#952200: libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
Source: libvirt-dbus Version: 1.3.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/tests' > PASS: test_util > PASS: test_interface.py > PASS: test_network.py > PASS: test_domain.py > PASS: test_nodedev.py > PASS: test_storage.py > FAIL: test_connect.py > == >libvirt-dbus 1.3.0: tests/test-suite.log > == > > # TOTAL: 7 > # PASS: 6 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: test_connect.py > = > > = test session starts > == > platform linux -- Python 3.7.6, pytest-4.6.9, py-1.8.1, pluggy-0.13.0 > rootdir: /<>/tests > collected 34 items > > test_connect.py F. > [100%] > > === FAILURES > === > ___ TestConnect.test_connect_node_device_create_xml > > Fixture "node_device_create" called directly. Fixtures are not meant to be > called directly, > but are created automatically when test functions request them as parameters. > See https://docs.pytest.org/en/latest/fixture.html for more information about > fixtures, and > https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly > about how to update your code. > = 1 failed, 33 passed in 3.89 seconds > == > FAIL test_connect.py (exit status: 1) > > > Testsuite summary for libvirt-dbus 1.3.0 > > # TOTAL: 7 > # PASS: 6 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See tests/test-suite.log > Please report to libvir-l...@redhat.com > > make[4]: *** [Makefile:767: test-suite.log] Error 1 > make[4]: Leaving directory '/<>/tests' > make[3]: *** [Makefile:875: check-TESTS] Error 2 > make[3]: Leaving directory '/<>/tests' > make[2]: *** [Makefile:991: check-am] Error 2 > make[2]: Leaving directory '/<>/tests' > make[1]: *** [Makefile:461: check-recursive] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/libvirt-dbus_1.3.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
