From: Szymon Janc <szymon.janc@tieto.com>
To: Sebastian Chlad <sebastian.chlad@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/pts: RFCOMM PTS update.
Date: Wed, 30 Jul 2014 11:26:24 +0200 [thread overview]
Message-ID: <13529513.ev1i7PCfTT@uw000953> (raw)
In-Reply-To: <1406643138-16988-1-git-send-email-sebastian.chlad@tieto.com>
Hi Sebastian,
On Tuesday 29 of July 2014 16:12:18 Sebastian Chlad wrote:
> Number of issues on PTS 5.2 for RFCOMM found. Problems with Credits
> (PTS issue #12421), Channel disconnect (PTS issue #12414), accepting
> UIH and UA frames (PTS issue #12397).
> ---
> android/pts-rfcomm.txt | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/android/pts-rfcomm.txt b/android/pts-rfcomm.txt
> index b96caab..9bfc7a2 100644
> --- a/android/pts-rfcomm.txt
> +++ b/android/pts-rfcomm.txt
> @@ -17,17 +17,21 @@ Test Name Result Notes
> TC_RFC_BV_01_C PASS rctest -n -P 1 <btaddr>
> TC_RFC_BV_02_C PASS rctest -r -P 1
> TC_RFC_BV_03_C PASS rctest -r -P 1
> -TC_RFC_BV_04_C FAIL
> +TC_RFC_BV_04_C FAIL PTS issue #12421
> + PTS issue #12414
> NOTE: DISC on DLC is expected; IUT disconnects
> rfcomm session (close)
> -TC_RFC_BV_05_C INC
> +TC_RFC_BV_05_C PASS rctest -n -P 4 <btaddr>
> + Note: test requires IUT to connect on the given
> + channel. sdptool browse <btaddr> to check the
> + channel.
> TC_RFC_BV_06_C PASS rctest -r -P 1
> TC_RFC_BV_07_C PASS rctest -r -P 1
> -TC_RFC_BV_08_C INC
> +TC_RFC_BV_08_C INC PTS issue #12397
> NOTE: Incorrect frame type sent in response to
> the DISC command
> TC_RFC_BV_11_C PASS rctest -r -P 1
> -TC_RFC_BV_13_C FAIL
> +TC_RFC_BV_13_C FAIL PTS issue #12397
> NOTE: IUT sent the correct frame type (UIH)
> but the parameters did not match the
> requirements
> @@ -35,7 +39,7 @@ TC_RFC_BV_14_C N/A
> TC_RFC_BV_15_C PASS rctest -r -P 1
> TC_RFC_BV_17_C PASS rctest -d -P 1
> TC_RFC_BV_19_C PASS
> -TC_RFC_BV_21_C INC
> -TC_RFC_BV_22_C INC
> -TC_RFC_BV_25_C INC
> +TC_RFC_BV_21_C INC PTS issue #12421
> +TC_RFC_BV_22_C INC PTS issue #12421
> +TC_RFC_BV_25_C INC PTS issue #12421
> -------------------------------------------------------------------------------
>
Applied, thanks.
--
Best regards,
Szymon Janc
next prev parent reply other threads:[~2014-07-30 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 14:12 [PATCH] android/pts: RFCOMM PTS update Sebastian Chlad
2014-07-30 9:26 ` Szymon Janc [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 14:06 Sebastian Chlad
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=13529513.ev1i7PCfTT@uw000953 \
--to=szymon.janc@tieto.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sebastian.chlad@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