Qemu test: use pmbootstrap --details-to-stdout (!1785)

The qemu test executes a pmbootstrap instance with
pmb.helpers.run.user(). Use the --details-to-stdout flag from now on for
the started pmbootstrap process, so it is not silent when downloading
packages with apk, and will therefore not run into the timeout of the
parent process (which kills processes that are silent for more than five
minutes by default).

This fixes the test in our CI infrastructure.
This commit is contained in:
Oliver Smith 2019-05-16 23:35:11 +02:00
parent 0c001567b6
commit f26eb0d9b8
No known key found for this signature in database
GPG Key ID: 5AE7F5513E0885CB
1 changed files with 7 additions and 4 deletions

View File

@ -69,11 +69,14 @@ def pmbootstrap_run(args, config, parameters, output="log"):
def pmbootstrap_yes(args, config, parameters):
"""
Execute pmbootstrap.py with a test pmbootstrap.conf, and pipe "yes"
into it (so we can do a fully automated installation, using "y" as
password everywhere).
Execute pmbootstrap.py with a test pmbootstrap.conf, and pipe "yes" into it
(so we can do a fully automated installation, using "y" as password
everywhere). Use --details-to-stdout to avoid the pmbootstrap process from
looking like it is hanging, when downloading packages with apk (otherwise
it would write no output, and get killed by the timeout).
"""
command = "yes | ./pmbootstrap.py -c " + shlex.quote(config)
command = ("yes | ./pmbootstrap.py --details-to-stdout -c " +
shlex.quote(config))
for parameter in parameters:
command += " " + shlex.quote(parameter)
return pmb.helpers.run.user(args, ["/bin/sh", "-c", command],