build results should be reported to results database

• Component: Tools / Tests
• Status: ASSIGNED ---

[Aakash Jain]

Build results (e.g.: pass/fail) should be reported to results database. Whenever build breaks, it would help in quickly finding the regression point.

[Jonathan Bedard]

This should be pretty easy to do!

My thinking on the best way to solve this problem was to have each project report to the results database as a "test". That way, the "suite" view would hold the total status of the build, and we would have a super clear (and machine parsable) history of not only when the build broke, but which projects broke it.

This basically involves having the build script we use in automation (so build-webkit) upload a json dictionary to results.webkit.org, whose format is outlined in https://results.webkit.org/documentation#API-Uploads

[Radar WebKit Bug Importer]

<rdar://problem/80627423>

[Aakash Jain]

If we have this, we can even have EWS check results database and avoid doing re-builds (compile-webkit-without-change step) in various scenarios, resulting in further speedup of EWS builder queues.