227793 2021-07-08 05:58:23 -0700 build results should be reported to results database 2023-10-17 14:49:51 -0700 1 1 1 Unclassified WebKit Tools / Tests Other Unspecified Unspecified ASSIGNED InRadar P2 Normal --- 1 aakash_jain jbedard aakash_jain ap ryanhaddad webkit-bug-importer oldest_to_newest 1775656 0 aakash_jain 2021-07-08 05:58:23 -0700 Build results (e.g.: pass/fail) should be reported to results database. Whenever build breaks, it would help in quickly finding the regression point. 1776330 1 jbedard 2021-07-12 08:34:57 -0700 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 1777182 2 webkit-bug-importer 2021-07-15 05:59:16 -0700 <rdar://problem/80627423> 1985697 3 aakash_jain 2023-10-17 14:49:51 -0700 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.