lakitu's cloud_FsLayout is way too restrictive |
|||
Issue descriptionlakitu's cloud_FsLayout is forcing us to update a random baseline whenever any files in bin dirs change. i don't know what the goal of this test is exactly, but it's way too restrictive atm. if there's a set of programs you want to make sure are always available, then you should search the base $PATH and make sure they're installed.
,
Feb 8 2018
We've been bitten in the past by binaries moving around; the specific example that motivated this test is b/65488897. A lot of our users rely on the absolute paths of binaries, often because of systemd limitations. The goal of this test was to alert us to file path changes before they make it into the image, and force us to evaluate if these changes are desirable. I don't think we really considered how it would impact teams outside of COS though, which was clearly an oversight. I think it makes sense to make the test far less restrictive for now while we redesign it. I'll send out a CL that does this.
,
Feb 8 2018
,
Feb 9 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/autotest-lakitu/+/2cb8dcf3829eb35629407940e6dd1fecc51fd6fa commit 2cb8dcf3829eb35629407940e6dd1fecc51fd6fa Author: Robert Kolchmeyer <rkolchmeyer@google.com> Date: Fri Feb 09 03:43:43 2018
,
Aug 1
|
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted