|
|
Descriptionbluetooth: Leak connections to paired devices
In order to avoid terminating connection to devices other parts of the
system might still be using we leak connections to paired devices.
BUG=630586
Committed: https://crrev.com/f1da372348cf570d8f1bb538b16d0ec3d47fbeb3
Cr-Commit-Position: refs/heads/master@{#420865}
Patch Set 1 #Patch Set 2 : bluetooth: Leak connections to paired devices #Patch Set 3 : Fix test #
Messages
Total messages: 30 (17 generated)
ortuno@chromium.org changed reviewers: + scheib@chromium.org
scheib: PTAL
The CQ bit was checked by ortuno@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
LGTM. Try jobs point out tests need updating.
scheib: Turns out there was a bit more to this. PTAL again.
The CQ bit was checked by ortuno@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
LGTM
The CQ bit was checked by ortuno@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by ortuno@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by ortuno@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by ortuno@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== bluetooth: Leak connections to paired devices In order to avoid terminating connection to devices other parts of the system might still be using we leak connections to paired devices. BUG=630586 ========== to ========== bluetooth: Leak connections to paired devices In order to avoid terminating connection to devices other parts of the system might still be using we leak connections to paired devices. BUG=630586 Committed: https://crrev.com/f1da372348cf570d8f1bb538b16d0ec3d47fbeb3 Cr-Commit-Position: refs/heads/master@{#420865} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/f1da372348cf570d8f1bb538b16d0ec3d47fbeb3 Cr-Commit-Position: refs/heads/master@{#420865} |