Tests are failing package install with "Could not find package(s)" |
||
Issue descriptionThis started in the tests as of 11281.0.0; but it's not every time so it could be from before that. I will manually try to reproduce it and figure out what's going on here. The only thing I saw changed in the CLs was the addition of the SyncTimes test...which I don't think would impact this at all.
,
Nov 26
I slightly tweaked vsh behavior with https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1332907 It's possible that's interfered with copying the package in.
,
Nov 26
I'm pretty sure it's the time sync. There's a test for the package info which runs right before the install test, and the package info one isn't failing at all...so the .deb file was copied fine. I'm doing a CL right now to change the time sync so this isn't a problem anymore.
,
Nov 26
To add more context to that...when we did the clock sync test; it was setting it to the epoch and then back to the current time. That was triggering the apt-daily activity which then was somehow interfering with the install (I would have expected an error with the dpkg lock; but maybe the 'could not find package(s)' relates to that somehow). The fix will be to just set the clock back one hour and then sync it and verify it's at the current time. Based on the log, that won't cause anything with apt-daily to fire during the testing.
,
Nov 28
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/f4f6bbe60eeb64e9d9af9302bc3e5f76e04ba3e5 commit f4f6bbe60eeb64e9d9af9302bc3e5f76e04ba3e5 Author: Jeffrey Kardatzke <jkardatzke@google.com> Date: Wed Nov 28 03:14:17 2018 tast-tests: Fix test failure with installing packages There was a new failure where installing from a .deb file would fail a lot of the time. This was because we added a time sync test which was setting the clock backwards to the epoch and then to the current time. That would then end up firing the apt-daily task which would interfere with the package install. The fix for this is to just disable the apt-daily and apt-daily-upgrade systemd timers during testing so that we don't get conflicts from those. BUG= chromium:908527 TEST=tast run vm.CrostiniStartEverything Change-Id: I942a2ee7524c789791a3c0e75eddc1e238e03bc4 Reviewed-on: https://chromium-review.googlesource.com/1351672 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/f4f6bbe60eeb64e9d9af9302bc3e5f76e04ba3e5/src/chromiumos/tast/local/bundles/cros/vm/crostini_start_everything.go
,
Nov 28
|
||
►
Sign in to add a comment |
||
Comment 1 by jkardatzke@chromium.org
, Nov 26