Your message dated Mon, 7 Apr 2025 21:29:34 +0100
with message-id <7e774df8-3fdd-4a61-966b-0a92f7627...@zoho.com>
and subject line Re: Bug#1102286: pagure: FTBFS: lots of failing tests
has caused the Debian Bug report #1102286,
regarding pagure: FTBFS: lots of failing tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1102286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pagure
Version: 5.14.1+dfsg-7
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_api_pr_private_repo_add_comment
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_api_private_repo_fork
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_api_private_repo_pr_add_flag
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_api_private_repo_pr_close
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_api_private_repo_pr_merge
FAILED
tests/test_pagure_flask_api_ui_private_repo.py::PagurePrivateRepotest::test_private_pr
FAILED
tests/test_pagure_flask_ui_fork.py::PagureFlaskForktests::test_new_request_pull_filename_unicode
FAILED
tests/test_pagure_flask_ui_plugins_mirror.py::PagureFlaskPluginMirrortests::test_setting_up_mirror
FAILED tests/test_pagure_lib_git.py::PagureLibGittests::test_update_git_requests
FAILED
tests/test_pagure_lib_git_diff_pr.py::PagureFlaskForkPrtests::test_diff_pull_request
FAILED
tests/test_pagure_lib_git_diff_pr.py::PagureFlaskForkPrtests::test_diff_pull_request_updated
FAILED
tests/test_pagure_lib_git_diff_pr.py::PagureFlaskForkPrtests::test_get_pr_info
FAILED
tests/test_pagure_lib_git_diff_pr.py::PagureFlaskForkPrtests::test_get_pr_info_raises
FAILED
tests/test_pagure_lib_git_diff_pr.py::PagureFlaskForkPrtests::test_two_diff_pull_request_sequentially
= 14 failed, 1605 passed, 67 skipped, 45 deselected, 131519 warnings in
10363.57s (2:52:43) =
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd
/<<PKGBUILDDIR>>/.pybuild/cpython3_3.13_pagure/build; python3.13 -m pytest -k
'not test_style and not test_upload_issue_virus and not
test_dumping_reloading_ticket and not test_plugin and not test_delete_repo'
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.13
returned exit code 13
make: *** [debian/rules:14: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202504/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:pagure, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
This looks like #1101621. (Which was easy to not notice because I
reassigned it without adding an affects, sorry.) As described there, it
should be fixed in python3-billiard 4.2.1-2.
If it continues to fail after installing that, please reopen the bug.
--- End Message ---
