unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan <stefan-guix@vodafonemail.de>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 43534@debbugs.gnu.org
Subject: bug#43534: qemu-minimal-5.1.0 fails to build during test phase on aarch64
Date: Sun, 20 Sep 2020 23:36:36 +0200	[thread overview]
Message-ID: <56B769EB-B804-495F-9091-E4E95A5CBB68@vodafonemail.de> (raw)
In-Reply-To: <87bli0e2qw.fsf@gmail.com>

Hi Maxim!

> Do you think this is a regression?  I doubt so, because even before
> pushing the update to 5.1.0, the test suite of qemu (not qemu-minimal)
> was failing on master.

I don’t know. Until today I always got a substitute. There was at least a successful build in late August.

http://ci.guix.gnu.org/search?query=system%3Aaarch64-linux+spec%3Aguix-master+qemu-minimal-5

> The error in the log you posted appear to be:
> 
> ERROR:tests/qtest/arm-cpu-features.c:508:test_query_cpu_model_expansion_kvm: assertion failed: (resp_has_props(_resp))
> ERROR arm-cpu-features - Bail out! ERROR:tests/qtest/arm-cpu-features.c:508:test_query_cpu_model_expansion_kvm: assertion failed: (resp_has_props(_resp))

I only searched for “FAIL”. :-)

The same test was passing in August.

http://ci.guix.gnu.org/log/391wav2qcfd1wkss2ssv408zhbgcxhq7-qemu-minimal-5.0.0

MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}  QTEST_QEMU_BINARY=arm-softmmu/qemu-system-arm QTEST_QEMU_IMG=qemu-img tests/qtest/arm-cpu-features -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="arm-cpu-features" 
PASS 1 arm-cpu-features /arm/arm/query-cpu-model-expansion
…
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}  QTEST_QEMU_BINARY=aarch64-softmmu/qemu-system-aarch64 QTEST_QEMU_IMG=qemu-img tests/qtest/arm-cpu-features -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="arm-cpu-features" 
PASS 1 arm-cpu-features /aarch64/arm/query-cpu-model-expansion
PASS 2 arm-cpu-features /aarch64/arm/kvm/query-cpu-model-expansion
PASS 3 arm-cpu-features /aarch64/arm/kvm/query-cpu-model-expansion/sve-off
PASS 4 arm-cpu-features /aarch64/arm/max/query-cpu-model-expansion/sve-max-vq-8
PASS 5 arm-cpu-features /aarch64/arm/max/query-cpu-model-expansion/sve-off


Bye

Stefan





  reply	other threads:[~2020-09-20 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20 15:43 bug#43534: qemu-minimal-5.1.0 fails to build during test phase on aarch64 Stefan
2020-09-20 18:12 ` Maxim Cournoyer
2020-09-20 21:36   ` Stefan [this message]
2020-09-26  6:05     ` Maxim Cournoyer
2020-09-26 11:14       ` Stefan
2020-09-27  0:31         ` Maxim Cournoyer
2020-09-27 12:38           ` Stefan
2021-03-16  1:36             ` Maxim Cournoyer
2021-05-28 18:08               ` bug#43500: qemu-minimal test suite crashes on armhf-linux, aarch64-linux Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56B769EB-B804-495F-9091-E4E95A5CBB68@vodafonemail.de \
    --to=stefan-guix@vodafonemail.de \
    --cc=43534@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).