History log of /system/bt/osi/test/AlarmTestHarness.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
d2e250824fca5c42b87b3b6f5fa19646ffa2d321 25-Aug-2015 Pavlin Radoslavov <pavlin@google.com> Add support for native kernel and callout wakelocks

* Moved wakelock-related code to osi/src/wakelock.c
The API is in osi/include/wakelock.h

* Use wakelock_set_os_callouts() to specify native kernel
or callout-based wakelock.
On Android, wakelock_set_os_callouts() is called to
set the bt_os_callouts_t callbacks into the Java layer.

* Renamed alarm_set_wake_lock_paths() to wakelock_set_paths()

Also, added Bluetooth Wakelock Statistics to the bugreport.
Sample output:

$ adb shell dumpsys bluetooth_manager
...
Bluetooth Wakelock Statistics:
Wakelock is acquired : false
Wakelock acquired/released count : 5 / 5
Wakelock acquired/released errors : 0 / 0
Wakelock last acquired time (ms) : 1524
Wakelock acquired time min/max/avg (ms) : 1511 / 8104 / 3167
Wakelock total acquired time (ms) : 15836
Bluetooth total run time (ms) : 44123

Bug: 26645431
Change-Id: I42bfb7db5b016719faea39e47ebc77c3ad02467b
/system/bt/osi/test/AlarmTestHarness.cpp
1b2bd2c8b5b7be80cb4ce0ecf4e021ad16e4a540 16-Nov-2015 Marie Janssen <jamuraa@google.com> tests: don't use bt_os_callouts for wakelocks

Introduces alarm_set_wake_lock_paths so wake lock paths can be changed
for testing, and adds AlarmTestHarness::WakeLockHeld to test whether a
wake lock is currently held.

Bug: 25387683
Change-Id: I9a41ae8266e252a3d436f8d41ea3f9e7ecb45cdc
/system/bt/osi/test/AlarmTestHarness.cpp
c196f214c5ae349ec2022f8d3cbaf56910b3b9f8 24-Sep-2015 Pavlin Radoslavov <pavlin@google.com> GKI cleanup - Moved GKI_get_os_tick_count() to OSI

* Renamed function GKI_get_os_tick_count() to time_get_os_boottime_ms()
and moved it to the OSI module: to the new file osi/src/time.c .
The corresponding header file is osi/include/time.h

* Added unit tests for function time_get_os_boottime_ms() in file
osi/test/time_test.cpp

* Removed "osi/include" from the list of paths to search for include
files. This is needed, because file name collision of "time.h"
in osi/include and the system <time.h>

Change-Id: I934be0c8f392150a352947326546bcf8aa070f97
/system/bt/osi/test/AlarmTestHarness.cpp
a9130e07646835a8550611bed32138ed79385a38 02-Jun-2015 Pavlin Radoslavov <pavlin@google.com> Moved the OSI alarm_shutdown() operations to alarm_cleanup()

Also, removed the OSI module's start_up and shut_down steps,
because now they are no-op.

Bug: 21558791
Change-Id: I24259b327f399af57c37937111158baa9704f644
/system/bt/osi/test/AlarmTestHarness.cpp
0d6a501d0517c186f11cbee294ae2c509073de91 23-May-2015 Pavlin Radoslavov <pavlin@google.com> Add missing clean_up step for the OSI module.

Now the OSI module's shut_down processing is split into "shut_down"
and "clean_up".

Previously, there was an ordering issue manipulating some of the
internal state during graceful shutdown/cleanup. Some of the modules
had two steps: shut_down, followed by clean_up, while other had only
shut_down step. This triggered the following assert in file alarm.c

alarm_cancel: assertion "alarms != NULL" failed

Bug: 21406940
Change-Id: Iab1f033a69cbff646a6b0f346760ae82f8b00b8f
/system/bt/osi/test/AlarmTestHarness.cpp
5da8446fd7c649350aef16d8a9e0d731a9526241 18-May-2015 Zach Johnson <zachoverflow@google.com> Fix AlarmTestHarness so alarm tests pass again

Ensures all alarm resources are torn down before the
test ends, so the allocation tracker is happy and
doesn't assert-fail the tests.

Also guard alarm_shutdown to make sure it only runs
if lazy_initialize was run (to avoid undefined behavior)

Change-Id: Iaf78fe85edd2fc65b9c5ee11c74665a11a3bc9ba
/system/bt/osi/test/AlarmTestHarness.cpp
ee2aa45def216a3c4d6a23481fa96f1b02a5de8c 27-Aug-2014 Zach Johnson <zachoverflow@google.com> Finish allocation tracking for the rest of osi

And found a memory leak in config, so it's doing its job! :)
/system/bt/osi/test/AlarmTestHarness.cpp
7edb61c6ac9f935489d8b6750f6fff9fa96b8cf8 21-Aug-2014 Zach Johnson <zachoverflow@google.com> Scope the lock_count variable in the alarm test harness
/system/bt/osi/test/AlarmTestHarness.cpp
2bbb33c648fd27233421a721e067d8c0e9012a7e 16-Aug-2014 Zach Johnson <zachoverflow@google.com> Refactor alarm tests to use a test harness

This improves the test writing experience for tests that rely on alarm code.
/system/bt/osi/test/AlarmTestHarness.cpp