• Bug#1102286: pagure: FTBFS: lots of failing tests

    From Santiago Vila@21:1/5 to All on Mon Apr 7 11:50:01 2025
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Mon Apr 7 22:50:01 2025
    This is a multi-part message in MIME format...

    Your message dated Mon, 7 Apr 2025 21:29:34 +0100
    with message-id <7e774df8-3fdd-4a61-966b-0a92f76272d2@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 owner@bugs.debian.org
    immediately.)


    --
    1102286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102286
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 7 Apr 2025 09:41:08 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-121.5 required=4.0 tests=ALL_TRUSTED,BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,HAS_PACKAGE,SPF_HELO_PASS,
    SPF_NONE,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,X_DEBBUGS_CC
    autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 13; hammy, 150; neutral, 109; spammy,
    0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--H*F:U*sanvila, 0.000-+--H*rp:U*sanvila Return-path: <sanvila@debian.org>
    Received: from mailly.debian.org ([2001:41b8:202:deb:6564:a62:52c3:4