I believe this is done now.

There seems to be some builders failing the test:
https://uberchromegw.corp.google.com/i/chromeos/builders/beaglebone-release/builds/1917
https://uberchromegw.corp.google.com/i/chromeos/builders/gale-release/builds/2140
https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-release/builds/3195
https://uberchromegw.corp.google.com/i/chromeos/builders/rainier-release/builds/353

I clicked through ~50 builds to check their status before giving up. Do you know any way to query the status of a given stage for all builders?

BTW, it looks like we should just check packages that are built by emerge. Namely, if a comp_path does not contain /portage/ then just ignore it. Otherwise, a newly added binary by gcc will fail the test.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/toolchain-utils/+/4bc22ee60558f57dce27ee2d35eba5aa40ec9a30

commit 4bc22ee60558f57dce27ee2d35eba5aa40ec9a30
Author: Caroline Tice <cmtice@google.com>
Date: Sun Mar 18 21:35:38 2018

[toolchain-utils] More whitelist updates.

We found a few more packages/files that need to be built with
GCC and are adding them to our debug_info_test whitelists.

BUG= chromium:813268 
TEST=Tested with remote tryjobs: lakitu-release, gale-release,
rainier-release, beaglebone-relase, fizz-release, cave-release.
All passed the DebugInfoTest stage.

Change-Id: I012d1620a85180f946c2ad2c8bbb175f5ef23e49
Reviewed-on: https://chromium-review.googlesource.com/967455
Commit-Ready: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/4bc22ee60558f57dce27ee2d35eba5aa40ec9a30/debug_info_test/ngcc_comp_path.whitelist
[modify] https://crrev.com/4bc22ee60558f57dce27ee2d35eba5aa40ec9a30/debug_info_test/ngcc_dso_path.whitelist