• Some severities to reconsider due to flaky tests

    From Santiago Vila@21:1/5 to All on Wed Apr 9 13:10:01 2025
    Dear Release Managers:

    Based on this reply by Paul:

    https://lists.debian.org/debian-devel/2025/04/msg00065.html

    I'd like to request that the severity of the following bugs is raised
    to serious again:

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072535

    (Reported by Paul as serious, downgraded later by the maintainer)

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562

    (Raised by Sebastian to serious, downgraded later by the maintainer)

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069402

    This is essentially the same as #1057562, except that it's
    for gcr version 3 which is in a different package.

    Note that both gcr and gcr4 are key packages, so a serious severity
    will not make the package to be removed.


    In all cases, disabling a flaky test should be easy enough.

    A brief explanation for the maintainers that we don't want
    flaky tests in trixie would also be nice.

    Thanks for your consideration.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Holger Levsen@21:1/5 to Santiago Vila on Thu Apr 10 13:50:02 2025
    On Wed, Apr 09, 2025 at 02:39:42PM +0200, Santiago Vila wrote:
    Remember: we do not hide problems. Somebody should look at this bug
    during Bug Squashing Parties, even if it does not make the package
    to be removed.

    what have severities to do with hiding problems?


    --
    cheers,
    Holger

    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
    ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
    ⠈⠳⣄

    I hear often the argument that we have lost the knowledge in the EU to be independent from the US. That is disinformation of big tech. All of their "innovation" is based on open source software, often written by public research institutions. When you visit #FOSDEM, you are literally at the hotspot of innovation. That knowledge is all around and open. We just need to pick it up and build our own economy around it. (https://mastodon.nl/@winfriedtilanus)

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

    iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmf3rjIACgkQCRq4Vgaa qhyOUg//awxr4On3YO7Sv+syUhtAiOeEzXEBaUXA9AqS8nXOIaVxSu0RriqKdiZU qABCmEmlPQXDihJOW9QJSX6oWqE0davtEXVNr2zwTk/bdVum3tDKKxDJs606Ou0G EKOCukERRmKj68FzBPWJ11F6IEfs+t/Y8c0A4CwRFgg4NxaiOYcTnEqZ4Kv2dofp yA+MeF3AqzjQdHsi6tlumOj3pqjoUo0Z8puhVDo3m5L75oV3
  • From Santiago Vila@21:1/5 to All on Thu Apr 10 14:40:01 2025
    El 10/4/25 a las 13:40, Holger Levsen escribió:
    On Wed, Apr 09, 2025 at 02:39:42PM +0200, Santiago Vila wrote:
    Remember: we do not hide problems. Somebody should look at this bug
    during Bug Squashing Parties, even if it does not make the package
    to be removed.

    what have severities to do with hiding problems?

    You are probably using the term "not hiding problems" as "the BTS is open
    for everybody to see". However, making bugs to be appear low in a
    list of bugs to be fixed, or even make them to not appear in the
    list at all, is also a way to hide them, as they are "less visible".

    In this case Paul says the gcr & gcr4 bugs are not RC anymore [*], but since he also asked the maintainer to apply the patch, I hope the maintainer
    can honor the request and we can continue with our other tasks.

    [*] I think with the criteria by Paul it was still RC when Jeremy downgraded it,
    which is the main reason I was complaining about this.

    Thanks.

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