Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] android/pts: Update PTS results for MCAP
Date: Mon, 03 Nov 2014 14:46:21 +0100	[thread overview]
Message-ID: <4453134.e3sOO7rWQK@uw000953> (raw)
In-Reply-To: <1415007076-5141-1-git-send-email-grzegorz.kolodziejczyk@tieto.com>

Hi Grzegorz,

On Monday 03 of November 2014 10:31:16 Grzegorz Kolodziejczyk wrote:
> Tested on android 4.4.4 against PTS 5.3
> ---
>  android/pts-mcap.txt | 114 +++++++++++++++++++++++++++++++++------------------
>  1 file changed, 75 insertions(+), 39 deletions(-)
> 
> diff --git a/android/pts-mcap.txt b/android/pts-mcap.txt
> index c35fefb..9d1fdcd 100644
> --- a/android/pts-mcap.txt
> +++ b/android/pts-mcap.txt
> @@ -1,7 +1,7 @@
>  PTS test results for MCAP
>  
> -PTS version: 5.2
> -Tested: 07-August-2014
> +PTS version: 5.3
> +Tested: 30-October-2014
>  Android version: 4.4.4
>  
>  Results:
> @@ -16,31 +16,42 @@ Note: Test were done with ssp enabled and in most of the cases requires pairing
>  -------------------------------------------------------------------------------
>  Test Name		Result	Notes
>  -------------------------------------------------------------------------------
> -TC_MCAP_CE_BV_01_C	PASS	mcaptest -C 4099 -D 4101 -dc <PTS addr>
> -TC_MCAP_CE_BV_02_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_CE_BV_03_C	PASS	mcaptest -C 4099 -D 4101 -c <PTS addr>
> -TC_MCAP_CE_BV_04_C	PASS	mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_CE_BV_01_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -dc <PTS addr>
> +TC_MCAP_CE_BV_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_CE_BV_03_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -c <PTS addr>
> +TC_MCAP_CE_BV_04_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
>  TC_MCAP_CM_ABT_BV_01_C	N/A
> -TC_MCAP_CM_ABT_BV_02_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_ABT_BV_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_ABT_BV_03_C	N/A
>  TC_MCAP_CM_DEL_BV_01_C	N/A
> -TC_MCAP_CM_DEL_BV_02_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_DEL_BV_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_DEL_BV_02_C	N/A
> -TC_MCAP_CM_DEL_BV_04_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_DEL_BV_04_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_DIS_BV_01_C	PASS	mcaptest -C 4099 -D 4101 -e 2 -f 2
>  TC_MCAP_CM_DIS_BV_02_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_CM_DIS_BV_03_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_DIS_BV_03_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_DIS_BV_04_C	PASS	mcaptest -C 4099 -D 4101 -e 2 -f 2
>  TC_MCAP_CM_DIS_BV_05_C	PASS	mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_REC_BV_01_C	N/A
> -TC_MCAP_CM_REC_BV_02_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_REC_BV_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CM_REC_BV_03_C	N/A
> -TC_MCAP_CM_REC_BV_04_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_REC_BV_04_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  				Note: It may be necessary to confirm pairing
>  					twice (second time when IUT is back in
>  					range).
>  TC_MCAP_CM_REC_BV_05_C	N/A
> -TC_MCAP_CM_REC_BV_06_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_CM_REC_BV_06_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  TC_MCAP_CS_ERR_BI_01_C	N/A
>  TC_MCAP_CS_ERR_BI_02_C	N/A
>  TC_MCAP_CS_ERR_BI_03_C	N/A
> @@ -53,31 +64,56 @@ TC_MCAP_CS_R_BV_01_I	N/A
>  TC_MCAP_CS_R_BV_02_I	N/A
>  TC_MCAP_CS_R_BV_03_C	N/A
>  TC_MCAP_CS_T_BV_04_C	N/A
> -TC_MCAP_ERR_BI_01_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_02_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_03_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_04_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_05_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_06_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_07_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_08_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_09_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_10_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_11_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_12_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_13_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_14_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_15_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_16_C	PASS	mcaptest -C 4099 -D 4101 -u
> -TC_MCAP_ERR_BI_17_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_18_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_ERR_BI_19_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_ERR_BI_20_C	PASS	mcaptest -C 4099 -D 4101 -g
> +TC_MCAP_ERR_BI_01_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_03_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_04_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_05_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_06_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_07_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_08_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_09_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_10_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_11_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_12_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_13_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_14_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_ERR_BI_15_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_16_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -u
> +TC_MCAP_ERR_BI_17_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_18_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_ERR_BI_19_C	N/A
> +TC_MCAP_ERR_BI_20_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -g
>  TC_MCAP_INV_BI_01_C	PASS	mcaptest -C 4099 -D 4101 -dc <PTS addr>
> -TC_MCAP_INV_BI_02_C	PASS	mcaptest -C 4099 -D 4101 -d
> -TC_MCAP_INV_BI_03_C	PASS	mcaptest -C 4099 -D 4101 -dc <PTS addr>
> -TC_MCAP_INV_BI_04_C	PASS	mcaptest -C 4099 -D 4101 -c <PTS addr>
> -TC_MCAP_INV_BI_05_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_INV_BI_06_C	PASS	mcaptest -C 4099 -D 4101
> -TC_MCAP_INV_BI_07_C	PASS	mcaptest -C 4099 -D 4101
> +TC_MCAP_INV_BI_02_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -d
> +TC_MCAP_INV_BI_03_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -dc <PTS addr>
> +TC_MCAP_INV_BI_04_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101 -c <PTS addr>
> +TC_MCAP_INV_BI_05_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_INV_BI_06_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
> +TC_MCAP_INV_BI_07_C	INC	PTS Issue #12693
> +				mcaptest -C 4099 -D 4101
>  -------------------------------------------------------------------------------
> 

Pushed. Thanks.

-- 
Best regards, 
Szymon Janc

      reply	other threads:[~2014-11-03 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  9:31 [PATCH v2] android/pts: Update PTS results for MCAP Grzegorz Kolodziejczyk
2014-11-03 13:46 ` 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=4453134.e3sOO7rWQK@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=grzegorz.kolodziejczyk@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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