All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Thomas Huth <thuth@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: tests: n810 arm failing
Date: Mon, 22 Feb 2021 16:35:00 +0100	[thread overview]
Message-ID: <cbf28177-bf94-2452-1c66-2f99a8f3dbf0@amsat.org> (raw)
In-Reply-To: <cef2f119-3612-65a0-d828-b480179dc3a9@amsat.org>

On 2/21/21 6:26 PM, Philippe Mathieu-Daudé wrote:
> Hi,
> 
> The n810 arm test failed on latest master:
> 
> https://gitlab.com/qemu-project/qemu/-/jobs/1045015424/artifacts/browse/build/tests/results/latest/test-results/26-tests_acceptance_machine_arm_n8x0.py_N8x0Machine.test_n810/
...
>     raise RuntimeError("Test interrupted by SIGTERM")
> 16:03:49 ERROR| RuntimeError: Test interrupted by SIGTERM
> 16:03:49 ERROR| ERROR
> 26-tests/acceptance/machine_arm_n8x0.py:N8x0Machine.test_n810 ->
> RuntimeError: Test interrupted by SIGTERM
> 16:03:49 INFO |
> Runner error occurred: Timeout reached

What we are missing here is we got a timeout ^
but return an error, so the debug.log is not shown:

> Original status: ERROR

...
> "tests/venv/lib/python3.7/site-packages/avocado/plugins/runner.py", line
> 77, in sigterm_handler\n    raise RuntimeError("Test interrupted by
> SIGTERM")\nRuntimeError: Test interrupted by SIGTERM\n', 'timeout': 90,
> 'whiteboard': '', 'phase': 'FINISHED', 'class_name': 'N8x0Machine',
> 'job_logdir': 'tests/results/job-2021-02-21T16.00-e662b93',
> 'job_unique_id': 'e662b936b3c04ad082359ee970534ac7ae7ec3bc', 'params': []}


      parent reply	other threads:[~2021-02-22 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 17:26 tests: n810 arm failing Philippe Mathieu-Daudé
2021-02-21 19:33 ` Peter Maydell
2021-02-22  6:25   ` Thomas Huth
2021-02-22  8:37     ` Philippe Mathieu-Daudé
2021-02-22 15:35 ` Philippe Mathieu-Daudé [this message]

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=cbf28177-bf94-2452-1c66-2f99a8f3dbf0@amsat.org \
    --to=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.