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

Issue 632002 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

"BluetoothSocketApiTest.Connect" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Jul 27 2016

Issue description

"BluetoothSocketApiTest.Connect" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKQsSBUZsYWtlIh5CbHVldG9vdGhTb2NrZXRBcGlUZXN0LkNvbm5lY3QM.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
 

Comment 1 by vabr@chromium.org, Jul 27 2016

Cc: keybuk@chromium.org
Components: OS>Systems>Bluetooth
Cc-ing keybuk@ who introduced this test.
Project Member

Comment 2 by bugdroid1@chromium.org, Jul 27 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a4707b0817c96d078e142643e2e33fcc38eea564

commit a4707b0817c96d078e142643e2e33fcc38eea564
Author: vabr <vabr@chromium.org>
Date: Wed Jul 27 15:20:13 2016

Disable BluetoothSocketApiTest.Connect

BUG=632002
TBR=keybuk@chromium.org,asargent@chromium.org
NOTRY=true

Review-Url: https://codereview.chromium.org/2180373006
Cr-Commit-Position: refs/heads/master@{#408131}

[modify] https://crrev.com/a4707b0817c96d078e142643e2e33fcc38eea564/extensions/browser/api/bluetooth_socket/bluetooth_socket_apitest.cc

Comment 3 by vabr@chromium.org, Jul 27 2016

Labels: -Sheriff-Chromium
Test was disabled, so bug leaves the sheriff queue.
Cc: scheib@chromium.org ortuno@chromium.org
+cc some folks who've been working on fizz bluetooth in case they may have been making infrastructure changes lately that might have caused this. 

Comment 5 by ortuno@chromium.org, Jul 27 2016

Owner: r...@chromium.org
Status: Assigned (was: Untriaged)
I believe rkc is now owner of chrome apps code.
Cc: -keybuk@chromium.org

Comment 7 by st...@chromium.org, Aug 24 2016

Owner: st...@chromium.org
is this still a P1?

Comment 9 by st...@chromium.org, Nov 4 2016

Labels: -Pri-1 Pri-2
Owner: r...@chromium.org
Cc: -scheib@chromium.org
Owner: jhawkins@chromium.org
James now owns connectivity in Chrome OS UI, over to him.

Sign in to add a comment