New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 592148 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Apr 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

chromeos-test-testauthkeys-mobbase failed to build due to collisions.

Project Member Reported by aaboagye@chromium.org, Mar 4 2016

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/guado_moblab-paladin/builds/1874

The guado_moblab failed in the BuildPackages step in the CQ. It looks like due to some file collisions...

stdio snippet from guado_moblab builder:
Started chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0 (logged in /tmp/chromeos-test-testauthkeys-mobbase-0.0.1-r0-qKKTqU)
=== Start output for job chromeos-test-testauthkeys-mobbase-0.0.1-r0 (0m21.1s) ===
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Emerging (1 of 1) chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0::mobbase for /build/guado_moblab/
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Running stacked hooks for pre_pkg_setup
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  *    sysroot_build_bin_dir ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  [ ok ]
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Running stacked hooks for pre_src_unpack
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  *    python_multilib_setup ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  [ ok ]
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Unpacking source...
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Source unpacked in /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/work
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Running stacked hooks for post_src_unpack
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  *    asan_init ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  [ ok ]
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Preparing source in /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/work ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Source prepared.
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Configuring source in /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/work ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Source configured.
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Compiling source in /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/work ...
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Source compiled.
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Test phase [not enabled]: chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0
chromeos-test-testauthkeys-mobbase-0.0.1-r0: 
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Install chromeos-test-testauthkeys-mobbase-0.0.1-r0 into /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/image/ category chromeos-base
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Completed installing chromeos-test-testauthkeys-mobbase-0.0.1-r0 into /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0/image/
chromeos-test-testauthkeys-mobbase-0.0.1-r0: 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Generating license for chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0 in /build/guado_moblab/tmp/portage/chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0
chromeos-test-testauthkeys-mobbase-0.0.1-r0: 14:57:49: INFO: Read licenses for chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0: BSD-Google
chromeos-test-testauthkeys-mobbase-0.0.1-r0: 14:57:49: INFO: chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0: using stock|cust license(s) BSD-Google
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/lib*/*.la
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/init.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/conf.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/logrotate.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/sandbox.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/share/bash-completion
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/id_rsa.pub
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/config
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/id_rsa
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/authorized_keys
chromeos-test-testauthkeys-mobbase-0.0.1-r0: ./root/.ssh/mobbase_id_rsa
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Done.
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Installing (1 of 1) chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0::mobbase to /build/guado_moblab/
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/lib*/*.la
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/init.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/conf.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/logrotate.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /etc/sandbox.d
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/share/bash-completion
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/share/man
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/share/info
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Removing /usr/share/doc
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * This package will overwrite one or more files that may belong to other
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * packages (see list below). You can use a command such as `portageq
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * owners / <filename>` to identify the installed package that owns a
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * file. If portageq reports that only one package owns a file then do
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * NOT file a bug report. A bug report is only useful if it identifies at
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * least two or more packages that are known to install the same file(s).
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * If a collision occurs and you can not explain where the file came from
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * then you should simply ignore the collision since there is not enough
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * information to determine if a real problem exists. Please do NOT file
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * a bug report at http://bugs.gentoo.org unless you report exactly which
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * two packages install the same file(s). See
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * solve the problem. And once again, please do NOT file a bug report
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * unless you have completely understood the above message.
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Detected file collision(s):
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/config
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/id_rsa.pub
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/id_rsa
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/authorized_keys
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Searching all installed packages for file collisions...
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Press Ctrl-C to Stop
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * chromeos-base/chromeos-test-testauthkeys-moblab-0.0.1:0::moblab
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/authorized_keys
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/config
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/id_rsa
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 	/build/guado_moblab/root/.ssh/id_rsa.pub
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * 
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * Package 'chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0'
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * NOT merged due to file collisions. If necessary, refer to your elog
chromeos-test-testauthkeys-mobbase-0.0.1-r0:  * messages for the whole content of the above message.
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>> Failed to install chromeos-base/chromeos-test-testauthkeys-mobbase-0.0.1-r0 to /build/guado_moblab/, Log file:
chromeos-test-testauthkeys-mobbase-0.0.1-r0: >>>  '/build/guado_moblab/tmp/portage/logs/chromeos-base:chromeos-test-testauthkeys-mobbase-0.0.1-r0:20160304-225744.log'
 
Owner: kevcheng@chromium.org
Status: Started (was: Untriaged)
I was thinking it was this CL: https://chromium-review.googlesource.com/#/c/328774/

Assigning to kevcheng@. Fix is in progress.
yeah sorry, tryjob in the pipeline, forgot to uprev the moblab ebuild which lead to the file collision
*I think* lead to the file collision.
Status: Fixed (was: Started)
Finally figured it out.

https://chromium-review.googlesource.com/#/c/328774/
Status: Verified (was: Fixed)
Bulk verified

Sign in to add a comment