On Wed, Apr 24, 2024 at 5:04 PM Santiago Vila <sanv...@debian.org> wrote: > > Jeremy Bícha wrote: > > It was also marked as severity important instead of RC because it does not > > affect official buildds. > > Not true: > > https://buildd.debian.org/status/logs.php?pkg=libsoup2.4&arch=all > > See also: > > https://buildd.debian.org/status/logs.php?pkg=gcr&arch=all > > and also: > > https://buildd.debian.org/status/logs.php?pkg=gcr4&arch=amd64 > > And regardless of the severity of the day, you were *explicitly* asked > by Sebastian Ramacher to disable *or* fix the flaky tests: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057562#17 > > Note that it's "or", nobody is asking you to act heroically and spend a time > that you don't have. We just want to build the packages without random > failures, > and for that it's enough to disable the tests that we know to be broken. > It can't be so much difficult.
I believe you are thinking about https://bugs.debian.org/1057562 The issue I am talking about now is https://bugs.debian.org/1064744 which is different and one I that I don't recall you or Sebastian interacting with me on. Also, whatever affects libsoup2.4/all on those builds is different as its test failures are different that what was reported here or at 1064744. There isn't currently a Debian bug for that issue. Thank you, Jeremy Bícha