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

Issue 685863 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocking:
issue 510287



Sign in to add a comment

bluetooth: Connection test broke with new testharness version

Project Member Reported by ortuno@chromium.org, Jan 27 2017

Issue description

src/third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error.html produces the following error:

CONSOLE ERROR: Uncaught (in promise) NetworkError: Authentication canceled.
This is a testharness.js-based test.
Harness Error. harness_status.status = 1 , harness_status.message = Authentication canceled.

In http://crrev.com/2648173006, qyearsley mentioned that it might be  Issue 662172 .
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 28 2017

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

commit 1ad4baf8846d1f6875ceb6b9fe95090720d756fb
Author: ortuno <ortuno@chromium.org>
Date: Sat Jan 28 00:49:05 2017

bluetooth: Fix failing connection test

https://github.com/w3c/testharness.js/commit/7716e2581a86dfd9405a9c00547a7504f0c7fe94
started failing tests if there were unhandled errors during tests. This caused
server/connect/garbage-collection-ran-during-error.html to fail because
'device.gatt.connect()' rejects.

BUG= 685863 

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

[delete] https://crrev.com/4a7c71ed22a116808b95765db383014399c45ed6/third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error-expected.txt
[modify] https://crrev.com/1ad4baf8846d1f6875ceb6b9fe95090720d756fb/third_party/WebKit/LayoutTests/bluetooth/server/connect/garbage-collection-ran-during-error.html

Comment 2 by ortuno@chromium.org, Jan 30 2017

Status: Fixed (was: Assigned)

Sign in to add a comment