From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: Fix not checking for valid hdev on bt_dev_{info,warn,err,dbg}
Date: Thu, 03 Mar 2022 14:48:30 -0800 (PST) [thread overview]
Message-ID: <622145be.1c69fb81.32a86.e294@mx.google.com> (raw)
In-Reply-To: <20220303211157.334337-1-luiz.dentz@gmail.com>
[-- 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=620122
---Test result---
Test Summary:
CheckPatch PASS 1.64 seconds
GitLint PASS 1.02 seconds
SubjectPrefix PASS 0.90 seconds
BuildKernel PASS 38.27 seconds
BuildKernel32 PASS 33.54 seconds
Incremental Build with patchesPASS 45.38 seconds
TestRunner: Setup PASS 584.82 seconds
TestRunner: l2cap-tester PASS 16.89 seconds
TestRunner: bnep-tester PASS 7.49 seconds
TestRunner: mgmt-tester PASS 124.54 seconds
TestRunner: rfcomm-tester FAIL 9.73 seconds
TestRunner: sco-tester PASS 9.52 seconds
TestRunner: smp-tester PASS 9.56 seconds
TestRunner: userchan-tester PASS 7.99 seconds
Details
##############################
Test: TestRunner: rfcomm-tester - FAIL - 9.73 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.196 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-03 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 21:11 [PATCH v2] Bluetooth: Fix not checking for valid hdev on bt_dev_{info,warn,err,dbg} Luiz Augusto von Dentz
2022-03-03 22:48 ` bluez.test.bot [this message]
2022-03-04 9:52 ` 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=622145be.1c69fb81.32a86.e294@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