staging test does not cover run_suite / dynamic suite cases that CQ uses |
||||
Issue descriptionCQ is broken by suite changes twice: Issue 787233 & 784564 It doesn't get tested in test_push.
,
Nov 27 2017
Issue 787233 reveals a gap in staging test.
,
Nov 27 2017
There are two separate issues The other one is https://bugs.chromium.org/p/chromium/issues/detail?id=784564 For https://bugs.chromium.org/p/chromium/issues/detail?id=787233, it would be caught by adding provision suite to test push. That is not needed now since provision suite is not deployed yet. For https://bugs.chromium.org/p/chromium/issues/detail?id=784564 staging test does not exercise the "check for minimum DUTs" logic.
,
Nov 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/64edf06917ba24f1ec7c31ceaa467fa7c81b4772 commit 64edf06917ba24f1ec7c31ceaa467fa7c81b4772 Author: Allen Li <ayatane@chromium.org> Date: Thu Nov 30 15:09:45 2017 [autotest] Test minimum DUTs logic in test push BUG= chromium:787251 TEST=None Change-Id: Ibb928d74c6111143a92667fd9a9feb174d1ea886 Reviewed-on: https://chromium-review.googlesource.com/792290 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Shuqian Zhao <shuqianz@chromium.org> [modify] https://crrev.com/64edf06917ba24f1ec7c31ceaa467fa7c81b4772/site_utils/test_push.py
,
Dec 4 2017
,
Jul 30
|
||||
►
Sign in to add a comment |
||||
Comment 1 by ayatane@chromium.org
, Nov 21 2017