From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: Fix not checking for valid hdev on bt_dev_{info,warn,err,dbg}
Date: Wed, 02 Mar 2022 18:38:22 -0800 (PST) [thread overview]
Message-ID: <62202a1e.1c69fb81.a6f0c.20a0@mx.google.com> (raw)
In-Reply-To: <20220302230858.444141-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1376 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=619731
---Test result---
Test Summary:
CheckPatch PASS 1.17 seconds
GitLint PASS 0.70 seconds
SubjectPrefix PASS 0.66 seconds
BuildKernel PASS 34.09 seconds
BuildKernel32 PASS 29.89 seconds
Incremental Build with patchesPASS 39.38 seconds
TestRunner: Setup PASS 581.60 seconds
TestRunner: l2cap-tester PASS 11.15 seconds
TestRunner: bnep-tester PASS 4.70 seconds
TestRunner: mgmt-tester PASS 91.13 seconds
TestRunner: rfcomm-tester FAIL 5.91 seconds
TestRunner: sco-tester PASS 5.97 seconds
TestRunner: smp-tester PASS 5.89 seconds
TestRunner: userchan-tester PASS 4.85 seconds
Details
##############################
Test: TestRunner: rfcomm-tester - FAIL - 5.91 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.125 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-03 2:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 23:08 [PATCH] Bluetooth: Fix not checking for valid hdev on bt_dev_{info,warn,err,dbg} Luiz Augusto von Dentz
2022-03-03 2:38 ` bluez.test.bot [this message]
2022-03-03 12:25 ` Marcel Holtmann
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=62202a1e.1c69fb81.a6f0c.20a0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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