Alright, I think I managed to get somewhere with the program's
configuration options: using an older reference config from
2019, shasta doesn't look to reserve itself unnecessary amounts
of memory, and the test should now go through. If this works,
we can forget about checking available memory
Hi Paul,
Paul Gevers, on 2023-12-03:
> 8GiB... that's not little, considering that that's what these hosts have as
> RAM (https://wiki.debian.org/ContinuousIntegration/WorkerSpecs).
[…]
> ci-worker-arm64-NN: -rw--- 1 root root 3.9G May 27 2022 /swap
[…]
> It's kbytes, memory, ratio == 0,
Hi Étienne,
On 03-12-2023 18:34, Étienne Mollier wrote:
1) why does it now suddenly start to (nearly always) fail across the
board on arm64 (in Debian, Ubuntu still seems fine), without changes to
the infrastructure that I know of?
I'm afraid I'm not sure what is up with shasta eating up more
Hi Paul,
> 1) why does it now suddenly start to (nearly always) fail across the
> board on arm64 (in Debian, Ubuntu still seems fine), without changes to
> the infrastructure that I know of?
I'm afraid I'm not sure what is up with shasta eating up more
memory on arm64 hosts of CI
Source: shasta
Version: 0.11.1-1
Severity: important
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package has an autopkgtest, great. However, it recently started
failing on arm64 in unstable, testing *and* stable. Until mid September
2023, most runs passed
5 matches
Mail list logo
