How to access logs for a build started by CQ

[Waldemar Rymarkiewicz]

Hi,

I have relatively trivial CL which cannot pass CQ due to some build errors.

How can I access build logs to verify it that was caused by my change?
I see the link in gerrit e.g.
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_minnie-paladin/builds/401
but seems like only Googlers can access (?)

Cheers,
/Waldek

[Richard Barnette]

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
>
>

[Waldemar Rymarkiewicz]

> 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.

I guess so. The change is trivial and pretty harmless, so I cannot
believe it can be the issue.

> So, your best bet is to keep clicking "+1 Ready", and cross
> your fingers for good luck.

The only thing I can do. Anyway good to know that someone is looking on this.

[David James]

Given that only Googlers can look at the CQ results, doesn't it make sense to lock down the +1 Ready bit to Googlers as well?

Seems like a Googler should be helping you get your change through the queue (so that they can examine the errors and verify your patch is not at fault)

[Mike Frysinger]

On Fri, Sep 16, 2016 at 7:04 PM, David James <david...@google.com> wrote:

that's a lot of excess work for Googlers with no upside that i can see.  the need for failures to be checked directly is uncommon overall, and easily rectified: they ask on the CL for someone to scrape the log.

-mike