On 07.01.23 12:40, Adrian Bunk wrote:
Does running the autopkgtests on 32-bit bring more benefits than hassle,
or should they be run only on 64-bit architectures?
As troublesome as the tests are on 32-bit, and as much as it would
probably be simpler to just blanket disable them in d/rules, I
On Fri, Dec 02, 2022 at 05:51:20PM +1300, Daniel Swarbrick wrote:
> Hi Paul,
>
> I have also noticed the fairly frequent failures of the memory-intensive
> tests on 32-bit, and I am doing my best to keep on top of them with t.Skip()
> patches where appropriate. Several of the tests result in the
Hi Paul,
I have also noticed the fairly frequent failures of the memory-intensive
tests on 32-bit, and I am doing my best to keep on top of them with
t.Skip() patches where appropriate. Several of the tests result in the 4
GiB memory footprint threshold being exceeded.
Prometheus itself is
Source: prometheus
Version: 2.33.5+ds1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package (because it
blocked glibc). I noticed that it regularly fails. At least on 32 bits
architectures, I think
4 matches
Mail list logo
