Saw this error several places in paladin, should extend the waiting time or increase the retry times?


https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fauron-paladin%2F9177%2F%2B%2Frecipes%2Fsteps%2FUnitTest%2F0%2Fstdout


https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fauron-paladin%2F9174%2F%2B%2Frecipes%2Fsteps%2FUnitTest%2F0%2Fstdout



chromite-0.0.2-r2735: 06:20:25: ERROR: The following 2 tests failed:
chromite-0.0.2-r2735:   scripts/export_to_gcloud_unittest
chromite-0.0.2-r2735:   scripts/virtualenv_wrapper_unittest
chromite-0.0.2-r2735:  * ERROR: chromeos-base/chromite-0.0.2-r2735::chromiumos failed (test phase):
chromite-0.0.2-r2735:  *   (no error message)
chromite-0.0.2-r2735:  * 
chromite-0.0.2-r2735:  * Call stack:
chromite-0.0.2-r2735:  *     ebuild.sh, line  93:  Called src_test
chromite-0.0.2-r2735:  *   environment, line 5880:  Called die
chromite-0.0.2-r2735:  * The specific snippet of code:
chromite-0.0.2-r2735:  *       cd "${CHROMITE_DIR}/cbuildbot" && sudo -u "${PORTAGE_USERNAME}" PATH="${CROS_WORKON_SRCROOT}/../depot_tools:${PATH}" ./run_tests || die
chromite-0.0.2-r2735:  * 
chromite-0.0.2-r2735:  * If you need support, post the output of `emerge --info '=chromeos-base/chromite-0.0.2-r2735::chromiumos'`,
chromite-0.0.2-r2735:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromite-0.0.2-r2735::chromiumos'`.
chromite-0.0.2-r2735:  * The complete build log is located at '/build/auron/tmp/portage/logs/chromeos-base:chromite-0.0.2-r2735:20170105-141709.log'.
chromite-0.0.2-r2735:  * For convenience, a symlink to the build log is located at '/build/auron/tmp/portage/chromeos-base/chromite-0.0.2-r2735/temp/build.log'.
chromite-0.0.2-r2735:  * The ebuild environment file is located at '/build/auron/tmp/portage/chromeos-base/chromite-0.0.2-r2735/temp/environment'.
chromite-0.0.2-r2735:  * Working directory: '/mnt/host/source/chromite/cbuildbot'
chromite-0.0.2-r2735:  * S: '/mnt/host/source/src/platform/../../chromite'
chromite-0.0.2-r2735: >>> Failed to emerge chromeos-base/chromite-0.0.2-r2735 for /build/auron/, Log file:
chromite-0.0.2-r2735: >>>  '/build/auron/tmp/portage/logs/chromeos-base:chromite-0.0.2-r2735:20170105-141709.log'
chromite-0.0.2-r2735: 
chromite-0.0.2-r2735:  * Messages for package chromeos-base/chromite-0.0.2-r2735 merged to /build/auron/:
chromite-0.0.2-r2735: 
chromite-0.0.2-r2735:  * ERROR: chromeos-base/chromite-0.0.2-r2735::chromiumos failed (test phase):
chromite-0.0.2-r2735:  *   (no error message)
chromite-0.0.2-r2735:  * 
chromite-0.0.2-r2735:  * Call stack:
chromite-0.0.2-r2735:  *     ebuild.sh, line  93:  Called src_test
chromite-0.0.2-r2735:  *   environment, line 5880:  Called die
chromite-0.0.2-r2735:  * The specific snippet of code:
chromite-0.0.2-r2735:  *       cd "${CHROMITE_DIR}/cbuildbot" && sudo -u "${PORTAGE_USERNAME}" PATH="${CROS_WORKON_SRCROOT}/../depot_tools:${PATH}" ./run_tests || die
chromite-0.0.2-r2735:  * 
chromite-0.0.2-r2735:  * If you need support, post the output of `emerge --info '=chromeos-base/chromite-0.0.2-r2735::chromiumos'`,
chromite-0.0.2-r2735:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromite-0.0.2-r2735::chromiumos'`.
chromite-0.0.2-r2735:  * The complete build log is located at '/build/auron/tmp/portage/logs/chromeos-base:chromite-0.0.2-r2735:20170105-141709.log'.
chromite-0.0.2-r2735:  * For convenience, a symlink to the build log is located at '/build/auron/tmp/portage/chromeos-base/chromite-0.0.2-r2735/temp/build.log'.
chromite-0.0.2-r2735:  * The ebuild environment file is located at '/build/auron/tmp/portage/chromeos-base/chromite-0.0.2-r2735/temp/environment'.
chromite-0.0.2-r2735:  * Working directory: '/mnt/host/source/chromite/cbuildbot'
chromite-0.0.2-r2735:  * S: '/mnt/host/source/src/platform/../../chromite'
=== Complete: job chromite-0.0.2-r2735 (3m30.0s) ===
Failed chromeos-base/chromite-0.0.2-r2735 (in 3m30.0s), retrying later.