EWS should run resultsdbpy tests. This would make sure that someone doesn't accidentally break resultsdbpy.
Created attachment 389909 [details]
Looks good to me. unit-tests needs minor change. Can you also deploy it on uat instance and verify.
Created attachment 389917 [details]
services_paths in CheckPatchRelevance needs to be updated as well. At:
Created attachment 389955 [details]
Created attachment 390032 [details]
Sample run: https://ews-build.webkit-uat.org/#/builders/1/builds/522
Comment on attachment 390032 [details]
Clearing flags on attachment: 390032
Committed r256021: <https://trac.webkit.org/changeset/256021>
All reviewed patches have been landed. Closing bug.
Deployed on production server, seems to be working fine, e.g.: https://ews-build.webkit.org/#/builders/20/builds/13802
(In reply to Aakash Jain from comment #11)
> Deployed on production server, seems to be working fine, e.g.:
I think that there is a question about if we should enable the full set of database tests (which take about 20 minutes), and I wanted to mention that possibility here so we have a record of the reason why I chose to only run the mock tests, which is basically because the full set of database tests take too long.