WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
ASSIGNED
227793
build results should be reported to results database
https://bugs.webkit.org/show_bug.cgi?id=227793
Summary
build results should be reported to results database
Aakash Jain
Reported
2021-07-08 05:58:23 PDT
Build results (e.g.: pass/fail) should be reported to results database. Whenever build breaks, it would help in quickly finding the regression point.
Attachments
Add attachment
proposed patch, testcase, etc.
Jonathan Bedard
Comment 1
2021-07-12 08:34:57 PDT
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
Comment 2
2021-07-15 05:59:16 PDT
<
rdar://problem/80627423
>
Aakash Jain
Comment 3
2023-10-17 14:49:51 PDT
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug