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 4 GiB memory > footprint threshold being exceeded.
4 GiB is the maximum address space limit, and it is typically only available on some architectures with 64-bit kernel (not on real 32-bit hardware). 2 GiB or 3 GiB are typical limits for available address space with 32-bit kernels (on MIPS it's 2 GiB even with a 64-bit kernel). > Prometheus itself is still usable on 32-bit, but obviously only up to a > certain size. The upstream developers don't seem to consider 32-bit when > writing unit tests, thus the regular addition of new tests which fail. Does running the autopkgtests on 32-bit bring more benefits than hassle, or should they be run only on 64-bit architectures? > Daniel. cu Adrian
