Currently joining cq_attempts to test_results by using completed_builds_legacy as an intermediary. Can bbucket_id be added to test_results directly so that it can be joined with cq_attempts?
I'm a little confused about bbucket_id and build_id. IIUC, bbucket_id is the universal unique integer number, and build_id is the string of format "bucket/builder/number" which supports both Buildbot and Luci builds. Is that correct?
integer identifier is not universal. It works only for buildbucket. Right now CQ has only those.
/me regrets inventing universal build ids because once we are on LUCI (soon!), we don't need them
Have another recipe-side change to actually specify the build_id so the uploader can pass it to the test-results server: https://chromium-review.googlesource.com/c/chromium/tools/build/+/903188 but I'm not so familiar with recipes. PTAL if you know recipes.
The "./recipes.py test train" command seems to have modified a lot more files than would seem necessary.
Comment 1 by no...@chromium.org
, Jan 29 2018