From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hdegoede@redhat.com
Subject: RE: Bluetooth: hci_core: Fix unbalanced unlock in set_device_flags()
Date: Wed, 02 Mar 2022 06:09:50 -0800 (PST) [thread overview]
Message-ID: <621f7aae.1c69fb81.1e0a4.91fc@mx.google.com> (raw)
In-Reply-To: <20220302134439.515377-1-hdegoede@redhat.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=619579
---Test result---
Test Summary:
CheckPatch PASS 1.68 seconds
GitLint PASS 0.97 seconds
SubjectPrefix PASS 0.85 seconds
BuildKernel PASS 36.20 seconds
BuildKernel32 PASS 31.72 seconds
Incremental Build with patchesPASS 43.70 seconds
TestRunner: Setup PASS 564.00 seconds
TestRunner: l2cap-tester PASS 15.37 seconds
TestRunner: bnep-tester PASS 7.22 seconds
TestRunner: mgmt-tester PASS 117.53 seconds
TestRunner: rfcomm-tester FAIL 9.09 seconds
TestRunner: sco-tester PASS 8.99 seconds
TestRunner: smp-tester PASS 8.92 seconds
TestRunner: userchan-tester PASS 7.47 seconds
Details
##############################
Test: TestRunner: rfcomm-tester - FAIL - 9.09 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.188 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-02 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 13:44 [PATCH] Bluetooth: hci_core: Fix unbalanced unlock in set_device_flags() Hans de Goede
2022-03-02 14:09 ` bluez.test.bot [this message]
2022-03-02 14:13 ` Hans de Goede
2022-03-02 19:13 ` Luiz Augusto von Dentz
2022-03-02 14:21 ` [PATCH] " 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=621f7aae.1c69fb81.1e0a4.91fc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hdegoede@redhat.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