[unit] Call gbinder_ipc_exit() when appropriate. Fixes JB#52595
If a test calls test_binder_set_looper_enabled(fd, TRUE) to enable processing of incoming data by the looper thread, the same thread may get picked up by the next test and swallow the reply before the transaction (for which the reply was intended) has been submitted. Which may cause that next test to either fail or (if the transaction was synchronous) block forever, stalling the build. Calling gbinder_ipc_exit() makes sure that looper thread terminates before the next test starts.
Showing
- unit/unit_client/unit_client.c 1 addition, 0 deletionsunit/unit_client/unit_client.c
- unit/unit_local_object/unit_local_object.c 4 additions, 0 deletionsunit/unit_local_object/unit_local_object.c
- unit/unit_remote_object/unit_remote_object.c 1 addition, 0 deletionsunit/unit_remote_object/unit_remote_object.c
- unit/unit_servicemanager/unit_servicemanager.c 2 additions, 0 deletionsunit/unit_servicemanager/unit_servicemanager.c
- unit/unit_servicemanager_aidl/unit_servicemanager_aidl.c 3 additions, 0 deletionsunit/unit_servicemanager_aidl/unit_servicemanager_aidl.c
- unit/unit_servicename/unit_servicename.c 2 additions, 0 deletionsunit/unit_servicename/unit_servicename.c
Please register or sign in to comment