parrot-release failures look like Issue 660409 ("ongoing staging issues")

Since version 8934.0.0, every candidate version has had at least one failure among lumpy-release, daisy-release and parrot-release. Almost every parrot-release build has failed since October 7. The other two builders usually succeed.

Lately the parrot-release failures are the staging issues from issue 660409, but previously SetupBoard was timing out; before that, BuildPackages [afdo_use] but those logs are gone.

As an aside

parrot-release has been failing for a long time, as #0 pointed out... why did LKGM succeed in build 1434?

parrot-release failed build: https://uberchromegw.corp.google.com/i/chromeos/builders/parrot-release/builds/3162

LKGM success: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/Chrome%20LKGM/builds/1434/steps/cros_best_revision/logs/stdio

00:04:49: INFO: RunCommand: /mnt/data/b/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-manifest-versions/builder-status/8934.0.0/lumpy-release
00:04:50: INFO: RunCommand: /mnt/data/b/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-manifest-versions/builder-status/8934.0.0/daisy-release
00:04:51: INFO: RunCommand: /mnt/data/b/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-manifest-versions/builder-status/8934.0.0/parrot-release
00:04:51: INFO: Version: 8934.0.0 Score: 2

Looking at /chromeos-manifest-versions/builder-status/8934.0.0/parrot-release, the status field (maybe? I don't know this format) was "inflight", not "fail" or "pass".

btw, filed issue 661385 about the "inflight" status meaning above.

Chrome LKGM finally updated yesterday, Nov 3, to 8955.0.0. (All 3 builders passed, although it looks like one of them was actually inflight when the the revision was scored.)

obsolete