From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, christophe.jaillet@wanadoo.fr
Subject: RE: Bluetooth: Don't assign twice the same value
Date: Wed, 02 Mar 2022 13:11:50 -0800 (PST) [thread overview]
Message-ID: <621fdd96.1c69fb81.7b41f.fa6a@mx.google.com> (raw)
In-Reply-To: <e2c2fe36c226529c99595370003d3cb1b7133c47.1646252285.git.christophe.jaillet@wanadoo.fr>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=619692
---Test result---
Test Summary:
CheckPatch PASS 0.72 seconds
GitLint PASS 0.42 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 38.87 seconds
BuildKernel32 PASS 34.65 seconds
Incremental Build with patchesPASS 47.41 seconds
TestRunner: Setup PASS 618.78 seconds
TestRunner: l2cap-tester PASS 16.73 seconds
TestRunner: bnep-tester PASS 7.50 seconds
TestRunner: mgmt-tester PASS 128.99 seconds
TestRunner: rfcomm-tester FAIL 9.62 seconds
TestRunner: sco-tester PASS 9.64 seconds
TestRunner: smp-tester PASS 9.54 seconds
TestRunner: userchan-tester PASS 7.80 seconds
Details
##############################
Test: TestRunner: rfcomm-tester - FAIL - 9.62 seconds
Run test-runner with rfcomm-tester
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Basic RFCOMM Socket Client - Write 32k Success Failed 0.224 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-02 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 20:18 [PATCH] Bluetooth: Don't assign twice the same value Christophe JAILLET
2022-03-02 21:11 ` bluez.test.bot [this message]
2022-03-02 21:36 ` Luiz Augusto von Dentz
2022-03-03 5:48 ` Christophe JAILLET
2022-03-14 22:00 ` Luiz Augusto von Dentz
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=621fdd96.1c69fb81.7b41f.fa6a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.