From: Stefan Berger <stefanb@linux.ibm.com>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Subject: Re: tpm-tis-device-swtpm-test timeout
Date: Tue, 15 Oct 2024 15:32:54 -0400 [thread overview]
Message-ID: <865424c1-f79c-44ad-b70f-8bf3e455e025@linux.ibm.com> (raw)
In-Reply-To: <87h69dqigg.fsf@suse.de>
On 10/15/24 3:22 PM, Fabiano Rosas wrote:
> 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.
So this here is failing for you every time?
QTEST_QEMU_BINARY=build/qemu-system-aarch64
./build/tests/qtest/tpm-tis-device-swtpm-test
This test would start swtpm. Do you see it running while this test is
running? It should show process like this running for a very short time
obviously [ while :; do ps aux | grep -v grep | grep swtpm; done ]:
stefanb 4087462 0.0 0.0 11040 3732 pts/6 S+ 15:30 0:00 swtpm
socket --tpmstate dir=/tmp/qemu-tpm-tis-device-swtpm-test.D3SLV2 --ctrl
type=unixio,path=/tmp/qemu-tpm-tis-device-swtpm-test.D3SLV2/sock --tpm2
stefanb 4087467 0.0 0.0 11040 3660 pts/6 S+ 15:30 0:00 swtpm
socket --tpmstate dir=/tmp/qemu-tpm-tis-device-swtpm-test.H1SLV2 --ctrl
type=unixio,path=/tmp/qemu-tpm-tis-device-swtpm-test.H1SLV2/sock --tpm2
>
> 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
>
next prev parent reply other threads:[~2024-10-15 19:33 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
2024-10-15 19:32 ` Stefan Berger [this message]
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=865424c1-f79c-44ad-b70f-8bf3e455e025@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
/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).