+dgarrett@ +vadimsh@ Guess what! What we've noticed today with LogDog + BQ has been reported 5 days ago.
Michael, go/logdog2bq is where we report that most greens with this exception are actually green (i guess most == all those on -dev instance of logdog).

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/a2f9d952767ed7c8d5c1ff0aedcc819d964c77c2

commit a2f9d952767ed7c8d5c1ff0aedcc819d964c77c2
Author: Michael Achenbach <machenbach@chromium.org>
Date: Mon Oct 30 12:45:10 2017

[CQ] Use non-luci fuchsia bots for cq experiment

This proceeds the experiment using the legacy bots, since luci bots
are blocked on  https://crbug.com/776734 .

NOTRY=true

Bug:  chromium:772816 ,  chromium:776734 
Change-Id: I7532e04e98a96d69dbeefcd6edf66fb0cddbe111
Reviewed-on: https://chromium-review.googlesource.com/743365
Reviewed-by: Sergiy Byelozyorov <sergiyb@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#49034}
[modify] https://crrev.com/a2f9d952767ed7c8d5c1ff0aedcc819d964c77c2/infra/config/cq.cfg

Looks like this was fixed. The build is reported to have 100% LUCI correctness: https://luci-migration.appspot.com/masters/tryserver.v8/builders/v8_fuchsia_rel_ng/.

Hum, hope it's really fixed. There is also this possibility:
- The broken code paths were only revealed when there was an sdk update.
- There was no update for a while and all bots got updated sdks over time...