Hi corentin, TCT testing is very important for us.
Only after finishing the related TCT testing, Bluetooth-Frwk will be accepted by Tizen.og. Therefore, can you debug TCT testing with us after finishing notification-service. Some issues are related with tizen-extension-crosswalk. We hope finish TCT testing as soon as possible too. Best Regard From: [email protected] [mailto:[email protected]] Sent: Friday, July 4, 2014 11:40 PM To: Zheng, Wu Cc: Le Foll, Dominique; Xu, Martin; Jia, Pei P; Gu, Chao Jie; Wu, JiangboX; [email protected] Subject: Re: [NTB] TCT testing bug Hi Zheng Wu, You're right ! I've sent a fix about setChangeListener/unsetChangeListener API. You can find the patch here: https://github.com/eurogiciel-oss/tizen-extensions-crosswalk/commit/0539f4536750bc3f9904df6e5ba207a9e4321105 Btw, I saw there are many blocked timeout issues. Sorry I can not perform and fix TCT issues on my side because I'm focalized on making NTB compliant with Tizen Common (using notification-service)... Best regards, Corentin On 07/04/2014 12:23 PM, Zheng, Wu wrote: Hi Corentin, 1. We are testing Bluetooth TCT cases. We meet many blocked timeout issues. The following issue has been checked by us. 2. In the test case of BluetoothAdapterChangeCallback_onnameChanged.html, we found that adapter.setChangeListener is registered. After 180000ns, if the cases can't get SetName successfully info from the listener of adapter.setChangeListener, It will be blocked timeout. adapter.setChangeListener is implemented by bluetooth_instance_bluez5.cc in tizen-extensions-crosswalk. No any Bluetooth CAPIs is invoked in the listener process. Can you check why the test case can't get the info from listener? Thanks. It blocked many test caases. Best Regards Zheng Wu
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
