Oh, <sigh>
I think getting you access is hard. :-(
It's been my sad duty to monitor the CQ failures this week.
I remember seeing your CL on some of the failures. Every
failure I looked at, I ruled your CL out as a possible
cause. Looking more closely, I still stand by that assessment:
I think you've just been unlucky.
Looking at the last failure, I see this message:
The following build(s) failed:
veyron_minnie-paladin: The HWTest [arc-bvt-cq] stage failed: ** HWTest failed (code 1) ** in
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-paladin/builds/401
This failure was probably caused by your change.
The automated diagnosis from this message is almost certainly
wrong. The failure in "veyron_minnie" was an ARC++ (Android)
specific test failure on an image that had been successfully
built. Your change, if it's going to cause problems at all,
should cause images not to build, rather than causing post-build
test failures. Moreover, your change successfully made it
through at least one build that passed that test.
So, your best bet is to keep clicking "+1 Ready", and cross
your fingers for good luck.
> Cheers,
> /Waldek
>
> --
> --
> Chromium OS Developers mailing list:
chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
>
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
>