isar-bootstrap failures with debian-buster targets

[Jan Kiszka <jan.kiszka@siemens.com>]

Hi all,

only on my machine so far, I'm seeing weird failures of buster-targeting
non-x86 builds, primarily armhf and also mipsel. The pattern is always
some out-of-memory inside apt during "apt-get update":

[...]
'/work/build/tmp/work/debian-buster-armhf/isar-bootstrap-target-1.0-r0/chroot-setup.sh' -> '/work/build/tmp/work/debian-buster-armhf/isar-bootstrap-target-1.0-r0/rootfs/chroot-setup.sh'
dpkg-divert: warning: diverting file '/sbin/start-stop-daemon' from an Essential package with rename is dangerous, use --no-rename
Hit:1 http://ftp.debian.org/debian buster InRelease
Get:2 http://ftp.debian.org/debian buster-updates InRelease [49.3 kB]
Get:3 http://security-cdn.debian.org buster/updates InRelease [39.1 kB]
Get:4 http://ftp.debian.org/debian buster/contrib Sources [43.1 kB]
Get:5 http://ftp.debian.org/debian buster/main Sources [7,827 kB]
Get:6 http://ftp.debian.org/debian buster/non-free Sources [86.2 kB]
Get:7 http://ftp.debian.org/debian buster/main Translation-en [5,967 kB]
Get:8 http://ftp.debian.org/debian buster/contrib Translation-en [44.7 kB]
Get:9 http://ftp.debian.org/debian buster/non-free Translation-en [88.3 kB]
Get:10 http://ftp.debian.org/debian buster-updates/main Sources [1,204 B]
Get:11 http://ftp.debian.org/debian buster-updates/main armhf Packages [884 B]
Get:12 http://ftp.debian.org/debian buster-updates/main Translation-en [600 B]
Reading package lists...
E: Could not read from /var/lib/apt/lists/partial/security.debian.org_dists_buster_updates_InRelease - getline (12: Cannot allocate memory)
E: The repository 'http://security.debian.org buster/updates InRelease' provides only weak security information.
WARNING: exit code 100 from a shell command.
ERROR: Function failed: do_bootstrap (log file is located at /work/build/tmp/work/debian-buster-armhf/isar-bootstrap-target-1.0-r0/temp/log.do_bootstrap.1156)

This is apparently caused by the getline here:

https://salsa.debian.org/apt-team/apt/blob/master/apt-pkg/contrib/fileutl.cc#L989

That just reads an absolutely valid line first line from a Release file
that is valid as well (identical to the file an x86 target downloaded
e.g.). ENOMEM makes zero sense /wrt to the overall system memory
available. It also does not correlate with parallel builds, I've also 
seen it when just building that single target. And, of course, it also 
succeeds when retrying often enough.

Anyone any idea? Build host is latest kas-project/kas-isar, i.e. a
Debian 10 instance.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux