Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Marcin Kraglak <marcin.kraglak@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/cts: Update CTS test results for Android 5.0
Date: Fri, 21 Nov 2014 09:15:10 +0100	[thread overview]
Message-ID: <2583652.Hra3FIedfq@uw000953> (raw)
In-Reply-To: <1416235809-12637-1-git-send-email-marcin.kraglak@tieto.com>

Hi Marcin,

On Monday 17 of November 2014 15:50:09 Marcin Kraglak wrote:
> ---
>  android/cts.txt | 50 +++++++++++++++++++++++++-------------------------
>  1 file changed, 25 insertions(+), 25 deletions(-)
> 
> diff --git a/android/cts.txt b/android/cts.txt
> index 9a7f651..68feabf 100644
> --- a/android/cts.txt
> +++ b/android/cts.txt
> @@ -1,15 +1,8 @@
>  Android Compatibility Test Suite results
>  
> -Tested: 11-July-2014
> -Android version: 4.4.4
> -CTS version: 4.4 R3
> -
> -Note:
> -CTS reliable write GATT tests require using CTS from master branch
> -or https://android-review.googlesource.com/99354 applied.
> -
> -(*) Due to bug in Bluedroid L2CAP implementation GATT server connect tests fails
> -without modified Linux kernel. Patches for Linux and/or Bluedroid are still TBD.
> +Tested: 17-November-2014
> +Android version: 5.0
> +CTS version: 5.0 r0.5
>  
>  -------------------------------------------------------------------------------
>  android.bluetooth.cts.BasicAdapterTest (automated tests)
> @@ -17,13 +10,13 @@ Test Name				Result	Notes
>  -------------------------------------------------------------------------------
>  testAndroidTestCaseSetupProperly	PASS
>  test_checkBluetoothAddress		PASS
> -test_enableDisable			PASS
> -test_getAddress				PASS
> -test_getBondedDevices			PASS
> +test_enableDisable			FAIL
> +test_getAddress				FAIL
> +test_getBondedDevices			FAIL
>  test_getDefaultAdapter			PASS
>  test_getName				PASS
>  test_getRemoteDevice			PASS
> -test_listenUsingRfcommWithServiceRecord	PASS
> +test_listenUsingRfcommWithServiceRecord	FAIL
>  -------------------------------------------------------------------------------

We now have updated SE Linux policy so those should pass now. Please retest.

>  
>  
> @@ -43,16 +36,23 @@ BLE Client Test:
>  	disconnect			PASS
>  BLE Server Test:
>  	add service			PASS
> -	connection			FAIL	(*) bluedroid issue.
> -	read characteristic request	FAIL	(*)
> -	write characteristic request	FAIL	(*)
> -	read descriptor request		FAIL	(*)
> -	write descriptor request	FAIL	(*)
> -	reliable write			FAIL	(*)
> -	disconnection			FAIL	(*)
> -Insecure Client				PASS
> -Insecure Server				PASS	Required kernel patch commit ID:
> +	connection			PASS
> +	read characteristic request	FAIL
> +	write characteristic request	FAIL
> +	read descriptor request		FAIL
> +	write descriptor request	FAIL
> +	reliable write			FAIL
> +	disconnection			FAIL
> +Insecure Client				FAIL
> +Insecure Server				FAIL	Required kernel patch commit ID:
>  						ba15a58b179ed76a7e887177f2b06de1
> -Secure Client				PASS
> -Secure Server				PASS
> +Secure Client				FAIL
> +Secure Server				FAIL
> +BLE Advertiser Test:
> +	BLE Hardware Scan Filter	FAIL
> +	BLE Tx Power Level		FAIL
> +BLE Scanner Test
> +	BLE Hardware Scan Filter	FAIL
> +	BLE Tx Power Level		FAIL
> +
>  -------------------------------------------------------------------------------
> 

-- 
Best regards, 
Szymon Janc

      reply	other threads:[~2014-11-21  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 14:50 [PATCH] android/cts: Update CTS test results for Android 5.0 Marcin Kraglak
2014-11-21  8:15 ` Szymon Janc [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2583652.Hra3FIedfq@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcin.kraglak@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox