All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Stefan Berger <stefanb@linux.ibm.com>, qemu-devel@nongnu.org
Subject: Re: tpm-tis-device-swtpm-test timeout
Date: Tue, 15 Oct 2024 16:22:55 -0300	[thread overview]
Message-ID: <87h69dqigg.fsf@suse.de> (raw)
In-Reply-To: <077cee03-efd0-4716-865a-b9990afb91a3@linux.ibm.com>

Stefan Berger <stefanb@linux.ibm.com> writes:

> On 10/15/24 2:11 PM, Fabiano Rosas wrote:
>> Hi Stefan,
>> 
>> I see the tpm-tis-device-swtpm test timing out, could you take a look?
>> 
>> qemu:qtest+qtest-aarch64 / qtest-aarch64/tpm-tis-device-swtpm-test time out (After 60.0 seconds)
>> 135/138 qemu:qtest+qtest-aarch64 /
>> qtest-aarch64/tpm-tis-device-swtpm-test TIMEOUT 60.01s killed by signal 11 SIGSEGV
>
> Is this something new or been happening for a while? Does it happen 
> consistently? I just build the master branch and ran the tests on a very 
> old machine, I mean 13 years old. The host runs Fedora 40 with 
> libtpms-0.96-6 + swtpm-0.9.0 from the distro:

It's the first time I see it. I can reproduce consistently by running
that test in a loop while make -j16 check is running in another window.

I'm on openSUSE Leap 15.5:

$ rpm -qa | grep libtpms
libtpms0-0.8.2-150300.3.9.1.x86_64

$ rpm -qa | grep swtpm
swtpm-0.7.3-150500.2.1.x86_64


  reply	other threads:[~2024-10-15 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 18:11 tpm-tis-device-swtpm-test timeout Fabiano Rosas
2024-10-15 18:58 ` Stefan Berger
2024-10-15 19:22   ` Fabiano Rosas [this message]
2024-10-15 19:32     ` Stefan Berger
2024-10-15 19:57       ` Fabiano Rosas
2024-10-15 20:57         ` Stefan Berger
2024-10-15 22:02           ` Fabiano Rosas
2024-10-15 23:35             ` Stefan Berger
2024-10-16  1:52               ` Stefan Berger
2024-10-16 14:03               ` Fabiano Rosas

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=87h69dqigg.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.ibm.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.