1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1104335: britney/debci: sometimes lists a non-regression fail as a

    From Rebecca N. Palmer@21:1/5 to All on Tue Apr 29 11:40:01 2025
    XPost: linux.debian.devel.release

    Package: release.debian.org

    The testing excuses list sometimes shows an autopkgtest as 'Regression',
    with the reference link going to an old (often old enough that the log
    is no longer available) passing migration-reference, when a newer migration-reference exists and failed (i.e. when the failure is not
    actually a regression).

    In all the cases I've noticed, this happened on only one architecture,
    even when the underlying 'reference used to pass, now fails' condition
    exists on more than one architecture.

    Instances I've noticed recently are r-bioc-keggrest/amd64 #1104334
    blocking r-base, pique/(I've forgotten which architecture) blocking
    r-base, and r-cran-plotly/riscv64 (listing https://ci.debian.net/packages/r/r-cran-plotly/testing/riscv64/58034134/
    as the reference) blocking r-cran-testthat. (The fact that these are
    all R packages is probably because that's where I've been looking
    recently, *not* a property of the bug itself. This is not an unblock
    request, as none of those are otherwise ready.)

    Workaround: Retrying the _reference_ test (using the link on the testing excuses page) makes it stop counting as a regression. Waiting *may*
    also do so.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Antonio Terceiro@21:1/5 to Paul Gevers on Tue Apr 29 19:20:01 2025
    XPost: linux.debian.devel.release

    On Tue, Apr 29, 2025 at 06:46:55PM +0200, Paul Gevers wrote:
    Hi Antonio,

    Can you imagine that the report below is due to the recent changes to debci? This is not the first report I'm getting and they started to come in after the improvement.

    Paul

    On 29-04-2025 11:31, Rebecca N. Palmer wrote:
    Package: release.debian.org

    The testing excuses list sometimes shows an autopkgtest as 'Regression', with the reference link going to an old (often old enough that the log
    is no longer available) passing migration-reference, when a newer migration-reference exists and failed (i.e. when the failure is not actually a regression).

    In all the cases I've noticed, this happened on only one architecture,
    even when the underlying 'reference used to pass, now fails' condition exists on more than one architecture.

    Instances I've noticed recently are r-bioc-keggrest/amd64 #1104334
    blocking r-base, pique/(I've forgotten which architecture) blocking r- base, and r-cran-plotly/riscv64 (listing https://ci.debian.net/packages/ r/r-cran-plotly/testing/riscv64/58034134/ as the reference) blocking r- cran-testthat.  (The fact that these are all R packages is probably
    because that's where I've been looking recently, *not* a property of the bug itself.  This is not an unblock request, as none of those are
    otherwise ready.)

    Workaround: Retrying the _reference_ test (using the link on the testing excuses page) makes it stop counting as a regression.  Waiting *may*
    also do so.

    Yes, this could be related. It turns out that jobs that are getting
    expired also get their "last updated" field changed and will now be
    returned by the API.

    I will revert the API change right away and think about a better
    solution later.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmgRCCoACgkQ/A2xu81G C96CSA/9EwTtHhkjplInN7uMeYpDfG4rP23pDz3bTmm0yl96gVLaekYGKfRyQTfo 4BDG4KQc/O1mIyzTJ+NJROlbpkEQ4QWdzrO5a7zkHklaulH5FROkxyql42jS8tTx gVu7DLoJOA0/cl3+VR1g0wKj7womYlsmhB1RjVaH6hHGILV3RRgHHki5x2kEcge7 HOv/H1I2LXGAX/cU0m04Fy1BrWWBMc8nJ+3QfumcKnETN9H8fmOZ8XofNNH/uibm 2zZBD0ild5KyXVhsPiNjewWx8JizGTBupRw5XM/L/BVZSpE2NEpXYpZiNIFaKlP/ XTf7A2JolOAZjyLQRIxoZE5GHyWYlrcGTnlF0Bn72rsuK0E1N93d+LDDZ75t+dKZ pxLTIFPZv1SGQBXOlX3WiYzg7XG555p2PDYsSodyGzOCcOGIp1MB04l8wbKLsqHV 6rO+EQXhXGbZpSuB2vDPEP62uVrb+GwdTOw8sG9fFkaiA2ULFLey0QpomrSaL4g2 e4/crxddoXwaXfqi5F2xyyxOLG1uozO0jllIjvJHA1v5DHzfwlcdp6dTdFMHL5n9 whMa2EeBD3ouGbrYjKSQamTFdPGe9OYxM8299ZJvAqjYuagJi9vSsXuYNQQGLu6K 3MhMiFhVp/AIHqt9IRqG9IVm5jduEtTgAWIwtewrm8swhndPXec=
    =gZc8
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rebecca N. Palmer@21:1/5 to All on Thu May 1 11:10:01 2025
    XPost: linux.debian.devel.release

    I've seen two more instances of this, r-bioc-keggrest/arm64 (https://ci.debian.net/packages/r/r-bioc-keggrest/testing/arm64/57700381/ listed as reference, underlying problem is #1104334) and
    r-cran-rmarkdown/arm64 (https://ci.debian.net/packages/r/r-cran-rmarkdown/testing/arm64/57691211/ listed as reference, though in that case the underlying problem #1104454
    was recent enough that there wasn't a failing reference yet).

    I don't know if they mean the fix in https://salsa.debian.org/release-team/britney2/-/commit/23be43224af93247b818c574bcd600e216d433cd
    didn't work, or that it hadn't been deployed yet.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)