From b7de12fc03c6abde6d39b8bb326fc97cbc455901 Mon Sep 17 00:00:00 2001 From: Robin Luk Date: Thu, 12 Nov 2020 03:52:30 +0000 Subject: kvm-test: adjust the check logic in TestWrongVCPU case Signed-off-by: Robin Luk --- pkg/sentry/platform/kvm/kvm_test.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'pkg') diff --git a/pkg/sentry/platform/kvm/kvm_test.go b/pkg/sentry/platform/kvm/kvm_test.go index e58acc071..a650877d6 100644 --- a/pkg/sentry/platform/kvm/kvm_test.go +++ b/pkg/sentry/platform/kvm/kvm_test.go @@ -412,9 +412,10 @@ func TestWrongVCPU(t *testing.T) { // Basic test, one then the other. bluepill(c1) bluepill(c2) - if c2.guestExits == 0 { + if c1.guestExits == 0 { + // Check: vCPU1 will exit due to redpill() in bluepill(c2). // Don't allow the test to proceed if this fails. - t.Fatalf("wrong vCPU#2 exits: vCPU1=%+v,vCPU2=%+v", c1, c2) + t.Fatalf("wrong vCPU#1 exits: vCPU1=%+v,vCPU2=%+v", c1, c2) } // Alternate vCPUs; we expect to need to trigger the -- cgit v1.2.3