Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(125)

Issues Search
    My Issues | Starred     Open | Closed | All

Issue 2188373002: DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer (Closed)

Created:
4 years, 4 months ago by ortuno
Modified:
4 years, 4 months ago
Reviewers:
CC:
blink-reviews, chromium-reviews, darin-cc_chromium.org, haraken, jam, jochen+watch_chromium.org, mlamouri+watch-content_chromium.org, mlamouri+watch-test-runner_chromium.org, ortuno+watch_chromium.org, Peter Beverloo, scheib+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@bluetooth-catch-and-connect
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer DO NOT SUBMIT * Navigate tree * Moar catches * Listener * Argument passing * Indentation * Save services and characteristics * GC only some services and characteristics from scheib: Are there any strategies we're after when running GC? If following my suggestion that we save some characteristics / services across tokens then we should also clear them during a GC -- but perhaps have a chance of only clearing some of them? BUG=

Patch Set 1 #

Messages

Total messages: 4 (4 generated)
ortuno
Description was changed from ========== DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer DO NOT SUBMIT BUG= ...
4 years, 4 months ago (2016-07-28 22:48:30 UTC) #1
ortuno
Description was changed from ========== DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer DO NOT SUBMIT * ...
4 years, 4 months ago (2016-08-02 15:54:09 UTC) #2
ortuno
Description was changed from ========== DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer DO NOT SUBMIT * ...
4 years, 4 months ago (2016-08-02 15:55:23 UTC) #3
ortuno
4 years, 4 months ago (2016-08-02 15:55:40 UTC) #4 
Description was changed from

==========
DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer

DO NOT SUBMIT

* Navigate tree
* Moar catches
* Listener
* Argument passing
* Indentation
* Save services and characteristics
* GC only some services and characteristics from scheib:
   Are there any strategies we're after when running GC? If following my
suggestion that we save some characteristics / services across tokens then we
should also clear them during a GC -- but perhaps have a chance of only clearing
some of them?


BUG=
==========

to

==========
DO NOT SUBMIT bluetooth-fuzzer: Draft fuzzer

DO NOT SUBMIT

* Navigate tree
* Moar catches
* Listener
* Argument passing
* Indentation
* Save services and characteristics
* GC only some services and characteristics from scheib:
   Are there any strategies we're after when running GC? If following my 
   suggestion that we save some characteristics / services across tokens then we
   should also clear them during a GC -- but perhaps have a chance of only
   clearing some of them?


BUG=
==========

Powered by Google App Engine
This is Rietveld 408576698