Swarming builds are not inserted into CIDB. |
|||
Issue descriptionSwarming builds can't be inserted into CIDB because that logic is tied to the current waterfall. This can be worked around for now by creating a placeholder waterfall value to use. "chromeos.swarming" PS: Is there any reason to have a "chromiumos.swarming" for external builds?
,
Sep 27 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/f0ae80d90078b665030ca45fc9561a82b464f4de commit f0ae80d90078b665030ca45fc9561a82b464f4de Author: Don Garrett <dgarrett@google.com> Date: Wed Sep 27 03:43:57 2017 waterfalls: Insert chromeos.swarming waterfall. Swarming doesn't really have a waterfall, but we use the value for a number of assorted things, so just create a placeholder waterfall for now. BUG= chromium:768025 TEST=run_tests Change-Id: I97923cdcec1aeb8e5f9e7c01e7b5fc5fa01605d6 Reviewed-on: https://chromium-review.googlesource.com/679676 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/f0ae80d90078b665030ca45fc9561a82b464f4de/scripts/cbuildbot.py [modify] https://crrev.com/f0ae80d90078b665030ca45fc9561a82b464f4de/lib/const/waterfall.py
,
Sep 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/89bcd5d027811e3d2fdfe5c6b2eaa61799f6f368 commit 89bcd5d027811e3d2fdfe5c6b2eaa61799f6f368 Author: Don Garrett <dgarrett@google.com> Date: Fri Sep 29 06:26:21 2017 cros tryjob: Don't set waterfall for swarming. I created a special swarming waterfall name, but forgot to remove the old hack value when sending swarming requests. BUG= chromium:768025 TEST=cros tryjob --swarming chromite-pre-cq Change-Id: I52c48d573b79b90df87f22621d927cbf27cc772e Reviewed-on: https://chromium-review.googlesource.com/687980 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Ningning Xia <nxia@chromium.org> [modify] https://crrev.com/89bcd5d027811e3d2fdfe5c6b2eaa61799f6f368/lib/remote_try.py
,
Oct 30 2017
,
Mar 6 2018
All swarming builds are now in either Prod or Debug CIDB. All non tryjobs are in Prod CIDB. Nearly all tryjobs in in Prod CIDB. A few "difficult" tryjob build configs are in Debug CIDB. These are roughly the configs "master-*-tryjob" and "precq-launcher-tryjob". Since the Legoland build details page is no longer fully dependent on CIDB information, I believe we can consider this fixed. jinjinl@ do you agree?
,
Mar 6 2018
Yes. The build details page should behave normally (only with slightly less info like recent related builds) even for builds not in Prod CIDB as long as they are in Buildbucket or Milo.BuildInfo. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Sep 27 2017