From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216177] kvm-unit-tests vmx has about 60% of failure chance
Date: Tue, 28 Jun 2022 00:28:15 +0000 [thread overview]
Message-ID: <bug-216177-28872-7AaU43xNGH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216177-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216177
Sean Christopherson (seanjc@google.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seanjc@google.com
--- Comment #1 from Sean Christopherson (seanjc@google.com) ---
It's vmx_preemption_timer_expiry_test, which is known to be flaky (though IIRC
it's KVM that's at fault).
Test suite: vmx_preemption_timer_expiry_test
FAIL: Last stored guest TSC (28067103426) < TSC deadline (28067086048)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-06-28 0:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 2:17 [Bug 216177] New: kvm-unit-tests vmx has about 60% of failure chance bugzilla-daemon
2022-06-28 0:28 ` bugzilla-daemon [this message]
2022-06-28 0:37 ` [Bug 216177] " Nadav Amit
2022-06-28 0:37 ` bugzilla-daemon
2022-06-28 1:19 ` bugzilla-daemon
2022-06-28 1:42 ` Nadav Amit
2022-06-28 4:39 ` Jim Mattson
2022-06-28 1:30 ` bugzilla-daemon
2022-06-28 1:42 ` bugzilla-daemon
2022-06-28 1:48 ` bugzilla-daemon
2022-06-28 2:19 ` bugzilla-daemon
2022-06-28 4:39 ` bugzilla-daemon
2022-06-28 6:11 ` bugzilla-daemon
2022-06-28 18:24 ` Jim Mattson
2022-06-28 18:24 ` bugzilla-daemon
2022-06-29 0:22 ` bugzilla-daemon
2022-06-29 2:32 ` Jim Mattson
2022-06-29 2:32 ` bugzilla-daemon
2022-06-29 2:50 ` bugzilla-daemon
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=bug-216177-28872-7AaU43xNGH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.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 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.