[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1897194] [NEW] Test failure in test-crypto-secret.c
From: |
Toolybird |
Subject: |
[Bug 1897194] [NEW] Test failure in test-crypto-secret.c |
Date: |
Fri, 25 Sep 2020 01:33:19 -0000 |
Public bug reported:
When running qemu test suite I'm seeing a test failure:
ERROR:../qemu/tests/test-crypto-secret.c:144:test_secret_keyring_good:
assertion failed: (key >= 0)
Host is Arch Linux running in the standard Arch build environment
(essentially an nspawn container).
I first noticed this at release of 5.1.0 but it's still there on current
trunk. For 5.1.0 I was able to sidestep the issue by building with
`--disable-keyring' but this no longer works (I think due to
9866a33cbb7046891dec3dcc9ca2015828673afe)
Any clues on what might be the cause? Not sure how to debug.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1897194
Title:
Test failure in test-crypto-secret.c
Status in QEMU:
New
Bug description:
When running qemu test suite I'm seeing a test failure:
ERROR:../qemu/tests/test-crypto-secret.c:144:test_secret_keyring_good:
assertion failed: (key >= 0)
Host is Arch Linux running in the standard Arch build environment
(essentially an nspawn container).
I first noticed this at release of 5.1.0 but it's still there on
current trunk. For 5.1.0 I was able to sidestep the issue by building
with `--disable-keyring' but this no longer works (I think due to
9866a33cbb7046891dec3dcc9ca2015828673afe)
Any clues on what might be the cause? Not sure how to debug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1897194/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1897194] [NEW] Test failure in test-crypto-secret.c,
Toolybird <=