Issue metadata
Sign in to add a comment
|
vm.StartCrosvm failing with "Didn't get VM prompt: context deadline exceeded" |
||||||||||||||||||||||||
Issue descriptionThe vm.StartCrosvm Tast test is failing consistently on canaries: http://stainless/search?test=%5Etast%5C.vm%5C.StartCrosvm%24&view=matrix&first_date=2018-09-15&last_date=2018-09-17 2018/09/16 10:36:02 Started test vm.StartCrosvm 2018/09/16 10:36:02 [10:36:01.292] Waiting for VM to boot 2018/09/16 10:38:02 [10:38:00.940] Error at start_crosvm.go:68: Didn't get VM prompt: context deadline exceeded 2018/09/16 10:38:02 [10:38:00.940] Stack trace: chromiumos/tast/local/bundles/cros/vm.StartCrosvm(0xc420122000) /build/eve-arcnext/tmp/portage/chromeos-base/tast-local-tests-cros-0.0.1-r173/work/tast-local-tests-cros-0.0.1/src/chromiumos/tast/local/bundles/cros/vm/start_crosvm.go:68 +0x364 chromiumos/tast/testing.(*Test).Run.func2(0xc420122000, 0xc4200ac150, 0xc4201aeb40) /build/eve-arcnext/tmp/portage/chromeos-base/tast-local-tests-cros-0.0.1-r173/work/tast-local-tests-cros-0.0.1/tast-base/src/chromiumos/tast/testing/test.go:114 +0x66 created by chromiumos/tast/testing.(*Test).Run /build/eve-arcnext/tmp/portage/chromeos-base/tast-local-tests-cros-0.0.1-r173/work/tast-local-tests-cros-0.0.1/tast-base/src/chromiumos/tast/testing/test.go:106 +0xc0 2018/09/16 10:38:02 [10:38:00.940] Failed to exec stop: context deadline exceeded 2018/09/16 10:38:02 Completed test vm.StartCrosvm in 2m0.369s with 1 error(s) Please consider running http://go/stainless-alert to receive email alerts about test failures. (There will hopefully be a better alerting system before too long.) Thanks!
,
Sep 18
Un-duping since this does not look like the TSC issue due to that it happens every single time.
,
Sep 19
Did a bisect and it looks like the CL to blame is https://chromium.googlesource.com/chromiumos/third_party/kernel/+/114a5608cde4197870d4f217c69f27ea20f9350c
,
Sep 19
Assigning to myself while we wait for mutexlox@ (who will be working on it) to get a chromium.org account.
,
Sep 26
,
Sep 27
After some more analysis...I think this is just an issue with how the test itself is looking for success so I'll look into that today.
,
Oct 1
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/2f05c69330879c875332b1b816dc0125251a4835 commit 2f05c69330879c875332b1b816dc0125251a4835 Author: Jeffrey Kardatzke <jkardatzke@google.com> Date: Sat Sep 29 07:27:31 2018 tast-tests: Fix localhost prompt checking in StartCrosvm Previously this test worked because the VM was logging out a line from the kernel after the bash prompt was shown, which then caused a line terminator to come through stdout. There was a kernel change which made that line come earlier, so we are not seeing the line terminator on stdout after the 'localhost #' prompt like we used to. This fixes that problem by scanning for bytes from stdout rather than lines. BUG= chromium:878908 TEST=tast run vm.StartCrosvm Change-Id: I3aebffe588a0c9a6ae9f012e9d74877cb1833455 Reviewed-on: https://chromium-review.googlesource.com/1249764 Commit-Ready: Jeffrey Kardatzke <jkardatzke@google.com> Tested-by: Jeffrey Kardatzke <jkardatzke@google.com> Reviewed-by: Dan Erat <derat@chromium.org> [modify] https://crrev.com/2f05c69330879c875332b1b816dc0125251a4835/src/chromiumos/tast/local/bundles/cros/vm/start_crosvm.go |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jkardatzke@chromium.org
, Sep 17Status: Duplicate (was: Assigned)