whesse
commented
4 years ago CL to remove last case where a configuration is run on two builders (on the same channel): https://dart-review.googlesource.com/c/sdk/+/144701 CL to start storing per-configuration results, logs, and flakiness: https://dart-review.googlesource.com/c/recipes/+/145060
When these are landed, remaining TODO:
- Add a check on test-matrix that two builders don't run the same configuration
- Move result processing to a cloud run service, instead of cloud functions. Do this at the same time as switching to per-configuration.
- Replace logs server with cloud run server, serve by configuration, fix links
- Remove by-builder data.
As part of a general change to processing data, or even before it, we should save results to cloud storage organized by configuration name, not builder name. We would still need to save it by build number, and be able to get the builder name from the data.
This requires that each configuration is run on only one builder.
This is related to a rewrite so that the results are processed on the builder, or on a server, not on cloud functions, and an entire results.json is processed at once.