Thanks for the catch. I suspected another patch in the range to be related since it was VPX only, but just found out that H264 was disabled for another reason. Relanding it here: https://codereview.webrtc.org/3002933002/.

After closer inspection it seems frame_analyzer is built as it should, at least for Release builds. The problem was that the new Debug builders took over the triggering of the Testers, which also have been running with debug builds for ~1 day.

This is being fixed in https://chromium-review.googlesource.com/620588

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/447498951dda678acfa8af0b306a5931a1394c08

commit 447498951dda678acfa8af0b306a5931a1394c08
Author: Henrik Kjellander <kjellander@chromium.org>
Date: Fri Aug 18 07:22:53 2017

WebRTC: Fix bug causing Debug builders to trigger testers

In https://chromium-review.googlesource.com/616736 a bug was introduced
that caused the debug builders to take over the triggering of the testers
instead of the Release builders.

Using platform+build config as key in the dictionary will restore the previous
behavior.

This would have been caught if we had the expectations around, but
it has been decided they're undesired, so we lost that protection.

BUG= 756741 
TBR=iannucci@chromium.org, ehmaldonado@chromium.org

Change-Id: I3054542929b7cbc3b32ee31ef72fdea81c7b3981
Reviewed-on: https://chromium-review.googlesource.com/620588
Reviewed-by: Henrik Kjellander <kjellander@chromium.org>
Commit-Queue: Henrik Kjellander <kjellander@chromium.org>

[modify] https://crrev.com/447498951dda678acfa8af0b306a5931a1394c08/scripts/slave/recipe_modules/chromium_tests/chromium_webrtc_fyi.py

I've now verified builds are back to normal.