Adding smut@ as well, because there's a fair amount of overlap between the //testing/buildbot/*.json files and the way the iOS recipes work (via ios/build/bots/*.json), and estaab@ and martiniss@ for interest in src-side recipes and expectations.

It's unclear exactly how this stuff would dovetail together w/ src-side recipes. Personally I'm not sure I agree that the JSON files are desirable in the end (cf. my well-documented rants against the -expected JSON files), but I can at least agree that we want them in the meantime and can leverage kbr@'s //content/test/gpu/generate_buildbot_json.py for this as well.

At one point I started looking at generating the rest of the src/testing/buildbot JSON files with a script similar to src/content/test/gpu/generate_buildbot_json.py. One issue I found was that there seemed to be quite a large number of exceptions -- in other words, it looked like the same exact tests weren't run in the exact same way across a large number of machines.

The first tool I was thinking of writing was something that ingested the JSON files and tried to automatically find commonalities between them.

Assigning to Dirk, please triage appropriately.

done :).