Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of jettrink@google.com

octopus-paladin:1154 failed

Builders failed on: 
- octopus-paladin: 
  https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941474462184124448

The build packages steps took less than 5 seconds, and the clean up step failed because the chroot was still in use. This seems more like an issue with the build step finishing so quickly and "successfully" .
 

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of jettrink@google.com

octopus-paladin:1154 failed

Builders failed on: 
- octopus-paladin: 
  https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941474462184124448

We could not delete the chroot because we couldn't unmount it with `umount -d /b/c/cbuild/repository/chroot`


06:29:32: INFO: Deleting autotest site packages.
06:29:32: INFO: Deleting chroot.
umount: /b/c/cbuild/repository/chroot: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))


This is most likely a transient issue