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

Issue 868331 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 728863
Closed: Jul 28
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

dragonegg paladin: Detected file collision - tpm_version

Project Member Reported by, Jul 27

Issue description

This paladin has been failing for several days.

trunks-0.0.1-r2548:  * Detected file collision(s):
trunks-0.0.1-r2548:  * 
trunks-0.0.1-r2548:  * 	/build/dragonegg/usr/sbin/tpm_version

See  for what looks like the same bug, never addressed.

I cannot find a candidate CL for this.

This one was merged before the failure started:

Components: OS>Packages
Labels: OS-Chrome
CL:*652771 is for a specific board (amd64-generic-cheets) which isn't used by any dragonegg related boards.

i agree it looks like the same bug.
Mergedinto: 728863
Status: Duplicate (was: Untriaged)
This seems to be the CL that caused the issue:

But, yeah, we should add a blocker, or wait for the paladin builder to clean itself up (isn't it supposed to do that and start from a clean chroot when it fails a few times in a row?)
+ Rajat, Shelley - can you find someone to own this? 
I am this week's sheriff, and it is still failing. 

I don't think I understand the issue, but I anyway have a CL out to disable TPM (for now):

For the actual fix for the underlying issue (having ability to switch from USE=tpm to USE=tpm2 without clearing /build/$BOARD, if that's how paladins buil): let's move discussion to  issue 728863 , where this one was merged.

Sign in to add a comment