New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 763052 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Add bluetooth suites to separate flaky from stable chameleon tests

Project Member Reported by rjahagir@chromium.org, Sep 7 2017

Issue description

We need our vendors to run our bluetooth suites but only with stable tests in them. We still want to schedule our flaky chameleon tests on our devices in lab however. This bug is a tracking bug to 1) Add additional scheduled bluetooth suites, 2) Categorize our existing tests into sanity/all/chameleon suites 3) Create new tests which will go into our flaky suite until they've stabilized. 

See go/bt-suites for more detail
 
Our current POA is to create two new suites, but only one will be scheduled. Bluetooth_chameleon will hold ALL of our chameleon bluetooth autotests while bluetooth_chameleon_sanity will only hold our stable chameleon bluetooth autotests. bluetooth_chameleon_sanity will be shared with our external vendors and kicked off manually. bluetooth_chameleon will run nightly on our 7 lab devices. 
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/29677ce58ea59ca46b6aff236976bb1f04999791

commit 29677ce58ea59ca46b6aff236976bb1f04999791
Author: Ruchi Jahagirdar <rjahagir@google.com>
Date: Thu Sep 14 02:28:28 2017

[Autotest] Adding new bluetooth suites

Adding bluetooth_chameleon and bluetooth_chameleon_sanity suites to separate flaky
and stable chameleon tests. Bluetooth_chameleon will contain all chameleon
tests using RN42 emulation kit. Bluetooth_chameleon_sanity contains the stable
tests with chameleon/RN42 and will not be scheduled.

BUG= chromium:763052 
TEST=None

Change-Id: Ib046aa6a1736dd5a315c09494cbf358b7384c299
Reviewed-on: https://chromium-review.googlesource.com/655803
Commit-Ready: Ruchi Jahagirdar <rjahagir@chromium.org>
Tested-by: Ruchi Jahagirdar <rjahagir@chromium.org>
Reviewed-by: Ruchi Jahagirdar <rjahagir@chromium.org>
Reviewed-by: Kalin Stoyanov <kalin@chromium.org>

[add] https://crrev.com/29677ce58ea59ca46b6aff236976bb1f04999791/test_suites/control.bluetooth_chameleon_sanity
[add] https://crrev.com/29677ce58ea59ca46b6aff236976bb1f04999791/test_suites/control.bluetooth_chameleon

Labels: OS-Chrome
Status: Verified (was: Started)
Project Member

Comment 6 by bugdroid1@chromium.org, Nov 2 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/infra/suite_scheduler/+/76bb6170165870580a09d9132b3e03cf897e4419

commit 76bb6170165870580a09d9132b3e03cf897e4419
Author: Ruchi Jahagirdar <rjahagir@google.com>
Date: Thu Nov 02 07:12:57 2017

[Autotest] Scheduling bluetooth_chameleon suite

Reorganizing bluetooth tests into bluetooth_chameleon suite to contain
tests which use chameleon/RN42 kit.

BUG= chromium:763052 
TEST=None

Change-Id: I19f0f40e68f1b6096015c24c33bcccf118bd3c81
Reviewed-on: https://chromium-review.googlesource.com/749683
Commit-Ready: Ruchi Jahagirdar <rjahagir@chromium.org>
Tested-by: Ruchi Jahagirdar <rjahagir@chromium.org>
Reviewed-by: Kalin Stoyanov <kalin@chromium.org>

[modify] https://crrev.com/76bb6170165870580a09d9132b3e03cf897e4419/configs/suite_scheduler.ini

Sign in to add a comment