qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: "Cédric Le Goater" <clg@kaod.org>, "Thomas Huth" <thuth@redhat.com>
Subject: Re: check-function failing on func-arm-arm_aspeed
Date: Mon, 28 Oct 2024 14:21:31 -0700	[thread overview]
Message-ID: <33cfeae7-d392-4d03-8f22-bb1a1e5dd48b@linaro.org> (raw)
In-Reply-To: <CAFEAcA_Z+o3HYfjapAeADAmjJqTYvswAfAbtj8i=3rSBDLwsyA@mail.gmail.com>

Hi Peter,

On 10/28/24 10:14, Peter Maydell wrote:
> Trying a "make check-functional" I find that the func-arm-arm_aspeed
> test seems to hit a timeout:
> 
> 18/18 qemu:func-thorough+func-arm-thorough+thorough /
> func-arm-arm_aspeed              TIMEOUT        600.08s   killed by
> signal 15 SIGTERM
> 
> This is with commit cea8ac78545a.
> 
> Does anybody else see this, or is it some oddity happening only
> on my local dev machine?
> 
> The "full log" in testlog-thorough.txt doesn't seem to be
> very full. All it has for this test is:
> 
> =================================== 18/18 ====================================
> test:         qemu:func-thorough+func-arm-thorough+thorough /
> func-arm-arm_aspeed
> start time:   16:54:50
> duration:     600.08s
> result:       killed by signal 15 SIGTERM
> command:      G_TEST_SLOW=1
> PYTHONPATH=/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/python:/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/tests/functional
> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> MALLOC_PERTURB_=238
> ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1
> MESON_TEST_ITERATION=1
> QEMU_TEST_QEMU_IMG=/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/arm-clang/qemu-img
> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
> QEMU_TEST_QEMU_BINARY=/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/arm-clang/qemu-system-arm
> QEMU_BUILD_ROOT=/mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/arm-clang
> /mnt/nvmedisk/linaro/qemu-from-laptop/qemu/build/arm-clang/pyvenv/bin/python3
> /mnt/nvmedisk/linaro/qemu-from-laptop/qemu/tests/functional/test_arm_aspeed.py
> ----------------------------------- stdout -----------------------------------
> TAP version 13
> ok 1 test_arm_aspeed.AST1030Machine.test_ast1030_zephyros_1_04
> ok 2 test_arm_aspeed.AST1030Machine.test_ast1030_zephyros_1_07
> ok 3 test_arm_aspeed.AST2x00Machine.test_arm_ast2400_palmetto_openbmc_v2_9_0
> ==============================================================================
> 
> Is it possible to get the log to include a pointer to the
> actual log for the test (including the guest console output)?
> It's hard to debug tests if they don't report what they're doing.
> 
> thanks
> -- PMM
> 

I didn't observe such failure in last run for my dev branch (which 
includes commit you mentioned) [1].

97/148 qemu:func-thorough+func-arm-thorough+thorough / 
func-arm-arm_aspeed                                         OK 
    141.44s   8 subtests passed

[1] 
https://github.com/pbo-linaro/qemu-ci/actions/runs/11559006814/job/32172747854

Regards,
Pierrick


  reply	other threads:[~2024-10-28 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 17:14 check-function failing on func-arm-arm_aspeed Peter Maydell
2024-10-28 21:21 ` Pierrick Bouvier [this message]
2024-11-04 12:12 ` Thomas Huth
2024-11-04 12:19   ` Cédric Le Goater
2024-11-04 13:16     ` Cédric Le Goater
2024-11-04 13:43       ` Cédric Le Goater
2024-11-04 15:12       ` Peter Maydell
2024-11-04 12:46   ` Daniel P. Berrangé
2024-11-04 13:01     ` Thomas Huth
2024-11-05 12:10   ` Thomas Huth

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

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

  git send-email \
    --in-reply-to=33cfeae7-d392-4d03-8f22-bb1a1e5dd48b@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=clg@kaod.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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.
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 NNTP newsgroup(s).