https://uberchromegw.corp.google.com/i/chromeos/builders/chell-chrome-pfq/builds/469
https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/1095
Both bots failed to install autotest packages with the same file conflicts error as follows.
autotest-tests-cheets-0.0.1-r387: >>> Failed to install chromeos-base/autotest-tests-cheets-0.0.1-r387 to /build/chell/, Log file:
autotest-tests-cheets-0.0.1-r387: >>> '/build/chell/tmp/portage/logs/chromeos-base:autotest-tests-cheets-0.0.1-r387:20170504-112329.log'
autotest-tests-cheets-0.0.1-r387:
autotest-tests-cheets-0.0.1-r387: * Messages for package chromeos-base/autotest-tests-cheets-0.0.1-r387 merged to /build/chell/:
autotest-tests-cheets-0.0.1-r387:
autotest-tests-cheets-0.0.1-r387: * This package will overwrite one or more files that may belong to other
autotest-tests-cheets-0.0.1-r387: * packages (see list below). You can use a command such as `portageq
autotest-tests-cheets-0.0.1-r387: * owners / <filename>` to identify the installed package that owns a
autotest-tests-cheets-0.0.1-r387: * file. If portageq reports that only one package owns a file then do
autotest-tests-cheets-0.0.1-r387: * NOT file a bug report. A bug report is only useful if it identifies at
autotest-tests-cheets-0.0.1-r387: * least two or more packages that are known to install the same file(s).
autotest-tests-cheets-0.0.1-r387: * If a collision occurs and you can not explain where the file came from
autotest-tests-cheets-0.0.1-r387: * then you should simply ignore the collision since there is not enough
autotest-tests-cheets-0.0.1-r387: * information to determine if a real problem exists. Please do NOT file
autotest-tests-cheets-0.0.1-r387: * a bug report at http://bugs.gentoo.org unless you report exactly which
autotest-tests-cheets-0.0.1-r387: * two packages install the same file(s). See
autotest-tests-cheets-0.0.1-r387: * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
autotest-tests-cheets-0.0.1-r387: * solve the problem. And once again, please do NOT file a bug report
autotest-tests-cheets-0.0.1-r387: * unless you have completely understood the above message.
autotest-tests-cheets-0.0.1-r387: *
autotest-tests-cheets-0.0.1-r387: * Detected file collision(s):
autotest-tests-cheets-0.0.1-r387: *
autotest-tests-cheets-0.0.1-r387: * /build/chell/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-r3036:0::chromiumos
autotest-tests-cheets-0.0.1-r387: * /build/chell/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: * Package 'chromeos-base/autotest-tests-cheets-0.0.1-r387' NOT merged
autotest-tests-cheets-0.0.1-r387: * due to file collisions. If necessary, refer to your elog messages for
autotest-tests-cheets-0.0.1-r387: * the whole content of the above message.
Comment 1 by jen...@chromium.org
, May 4 2017Status: Duplicate (was: Untriaged)