Kernel testing: Really run LTP? Or kill it |
|
Issue descriptionSee these: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/191912 https://bugs.chromium.org/p/chromium/issues/detail?id=354547 https://chromium-review.googlesource.com/332200 which mean that currently, we build an old version of LTP with lots of bugs [1], and then don't do anything with it. It looks like bug 354547 concluded with "we have no time to fix this." Except we still left all the build hanging around. So let's bite the bullet: either kill the build, or support it properly (and regularly run it again). So what'll it be? [1] e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=667204
,
Oct 27
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/f6eb58eae5f94b4cb612caac927b0288dcf4eeba commit f6eb58eae5f94b4cb612caac927b0288dcf4eeba Author: Brian Norris <briannorris@chromium.org> Date: Sat Oct 27 00:19:04 2018 autotest-all: stop building ltp We're not running it, and it causes build flake. We can start building it again if we're really going to use it. BUG=chromium:899051 TEST=precq Change-Id: I893b6a8eff8bba200b785e15bef2d88ac89b3f26 Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1300193 Reviewed-by: Mike Frysinger <vapier@chromium.org> [rename] https://crrev.com/f6eb58eae5f94b4cb612caac927b0288dcf4eeba/chromeos-base/autotest-all/autotest-all-0.0.1-r48.ebuild [modify] https://crrev.com/f6eb58eae5f94b4cb612caac927b0288dcf4eeba/chromeos-base/autotest-all/autotest-all-0.0.1.ebuild |
|
►
Sign in to add a comment |
|
Comment 1 by briannorris@chromium.org
, Oct 25