autotest-tests-cheets ebuild file collision failure |
||||
Issue descriptionBuild: https://luci-milo.appspot.com/buildbot/chromeos/cyan-paladin/2450 Snippet: autotest-tests-cheets-0.0.1-r387: * autotest-tests-cheets-0.0.1-r387: * /build/cyan/usr/local/build/autotest/server/site_tests/cheets_CTS/generate_controlfiles.py autotest-tests-cheets-0.0.1-r387: * autotest-tests-cheets-0.0.1-r387: * Searching all installed packages for file collisions... autotest-tests-cheets-0.0.1-r387: * autotest-tests-cheets-0.0.1-r387: * Press Ctrl-C to Stop autotest-tests-cheets-0.0.1-r387: * autotest-tests-cheets-0.0.1-r387: * chromeos-base/autotest-server-tests-0.0.2-r3037:0::chromiumos autotest-tests-cheets-0.0.1-r387: * /build/cyan/usr/local/build/autotest/server/site_tests/cheets_CTS/generate_controlfiles.py autotest-tests-cheets-0.0.1-r387: * Filing for annotations purposes, and also possible follow-up investigation. This smells a little like a strange failure in the autotest uprev/packaging logic.
,
May 4 2017
likely caused by https://chrome-internal-review.googlesource.com/c/368112/ ihf@ did this fix itself due to a later uprev, or was there a fix applied?
,
May 4 2017
all file moves should have a blocker in play even if things "eventually fix themselves". blockers keep flakes out, both on bots and on dev's systems.
,
May 5 2017
,
Jan 26 2018
Not an issue now |
||||
►
Sign in to add a comment |
||||
Comment 1 by akes...@chromium.org
, May 4 2017