Debian Bug report logs - #1103356
surf autopkgtest "command 2" is flaky on riscv64

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Ian Jackson <[email protected]>

To: [email protected]

Subject: surf autopkgtest "command 2" is flaky on riscv64

Date: Wed, 16 Apr 2025 19:24:02 +0100

Package: surf
Version: 2.1+git20240324-1
Severity: serious
Justification: Preventing migrations in ci.d.n

Hi.  I'm working on src:autopkgtest.  Currently, we're having a
problem with testing migration because the 2nd listed autopkgtest is
failing in ci.debian.net.  That's the one with the command
  timeout -v 10m xvfb-run debian/tests/test_http.py

Here's the logs for one such run:
  https://ci.debian.net/packages/s/surf/testing/riscv64/59960211/

This test apparently passed in the baseline but failed when run in the
migration test for autopkgtest 5.48.  But, autopkgtest.deb is not used
by that particular test case ("command2").  It's not even installed by
the CI test runner.

The migration test was triggered by the existence of the 3rd test
case, which *does* depend on autopkgtest, and also fails with similar
looking error messages.  That 3rd test case is marked flaky so isn't a
regression.  That test uses some files from autopkgtest's doc
directory as test cases.  That seems to be the only connection to
autopkgtest.ceb.

Note: it is important to distinguish the two autopkgtests in this
scenario:

1. src:autopkgtest whose possible testing migration triggered this
test run, and its autopkgtest.deb which is installed in the flaky surf
test case.  This is the autopkgtest that the test appears to impugn,
but which I think cannot be implicated in the blocking test failure.

2. The outer autopkgest used by ci.d.n to run all these tests.  ci.d.n
uses a fixed version of autopkgtest, not the version under test.

Looking at tracker.d.o the failure seems to be arch-specific, only
occurring on riscv64.  I think, probably, the test is simply flaky.

Please would you mark this 2nd test flaky too.  In the meantime I will
probably end up asking the release team to override it.

Ian.

-- 
Ian Jackson <[email protected]>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Message #10 received at [email protected] (full text, mbox, reply):

From: Debian FTP Masters <[email protected]>

To: [email protected]

Subject: Bug#1103356: fixed in surf 2.1+git20250419-1

Date: Sun, 20 Apr 2025 20:36:46 +0000

[Message part 1 (text/plain, inline)]

Source: surf
Source-Version: 2.1+git20250419-1
Done: Reiner Herrmann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
surf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reiner Herrmann <[email protected]> (supplier of updated surf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 20 Apr 2025 21:33:35 +0200
Source: surf
Architecture: source
Version: 2.1+git20250419-1
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann <[email protected]>
Changed-By: Reiner Herrmann <[email protected]>
Closes: 1012739 1103356
Changes:
 surf (2.1+git20250419-1) unstable; urgency=medium
 .
   * New upstream snapshot.
   * Refresh patches.
   * Bump Standards-Version to 4.7.2
   * Mark HTTP test as flaky as it frequently causes migration regressions in
     other packages (Closes: #1103356).
   * Force usage of x11 gdk backend as wayland is not supported
     (Closes: #1012739).
Checksums-Sha1:
 319659e6dcdf533a6ce2d2fa576b7ab5623ca985 2107 surf_2.1+git20250419-1.dsc
 035a3c32f21cf92f43138783e4a96e715a267f5f 21276 surf_2.1+git20250419.orig.tar.xz
 7d270d9cd65d2d821ba328b104fd07b8c49b0bde 11456 surf_2.1+git20250419-1.debian.tar.xz
 6ea6a41607562edc8057d0337e2110ca349af3cf 18551 surf_2.1+git20250419-1_source.buildinfo
Checksums-Sha256:
 949c1e9a59b36776035253a4346b811bd73b40b0fafee8014124ece6bb429f85 2107 surf_2.1+git20250419-1.dsc
 5d864a97d64536460f65d105afe78fb7c129723396b126e19d59ebd4df29c58e 21276 surf_2.1+git20250419.orig.tar.xz
 5c9ad7e21d4ebc4b04bd15e2deb28f457a8ba2ad6089ce1881ed047eb1c6db76 11456 surf_2.1+git20250419-1.debian.tar.xz
 d4a91c77992e9c0069eb11bc9aa17940434a8ad78dbfd21658fa0e88df2b18ad 18551 surf_2.1+git20250419-1_source.buildinfo
Files:
 38b9b014429cb76e6a7ae55e5eca8e25 2107 web optional surf_2.1+git20250419-1.dsc
 f4883bb1ac55fbb8931ae97dfa4df3ac 21276 web optional surf_2.1+git20250419.orig.tar.xz
 ad5aa881e0eac5903b189daf861bdfd0 11456 web optional surf_2.1+git20250419-1.debian.tar.xz
 0d8f9581fd640ce08ebdf91f6d69bed3 18551 web optional surf_2.1+git20250419-1_source.buildinfo

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

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAmgFTEYACgkQzPBJKNsO
6qcYbBAA0POPojsRODQLcFszE1ka26Yc9UXJ98D7peF2jpj5QzWfBK2TughVxkvD
S+V9C3DhoNk1GvtIAZQIvUTlbapewhj1Ad2czZO2SAhbCIS9lkAN4aiKP37cp9W+
UKNn2ABU7AD94EONCVKNf5Alcm5hKFufEn/WV8ibaOQqIXX7PScDgwode1atwBoi
DBFunWbkIz8QP7GfgoplLb6fDxXJKtNzmK3SQ9Q3eNEpMvNhQh4NLpTm0+S0SQLZ
xkp4v+IJyRXy0eIPiJjrI3QuO5ci9Vy3bn8HAbmR/z2s99/IeEas4mKV6P5dDzfL
6Y/TM2F9jI+n6VE5QPMuXvS67pxEPzYF7C56kZA+LKi7q6NsQtIDFHI6p878FdA9
/kvNPEAQMBlV9SbumWl/WrODREPhktITwhSaKyBBqlh8jofH8WBWnX3M/nInX9MS
ArzX+7S9UpdwMJE+D88fPEldkca0QkPxF3t+WMDY9blYpEwgcATyTSyGVETQPMNn
h6qJszDw92MPFuN6QVtjtcX1k+p7ZPJOS5zMoqvaSrWa9pD1liJtTE1PVoupu3lO
hTBnFvyvw6xBEOw6ffASqLpLaccpbme37mdZsR8e5o1roX78BhvxkfOr/QwPWJ8i
BDJ2X4/h7YxcjIDV1lj5MD53AYN1SgD2EMlax7/aRZrZDWSWxZk=
=E4gu
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.