All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yinghsu@chromium.org
Subject: RE: [v5] Bluetooth: Fix l2cap_disconnect_req deadlock
Date: Tue, 30 May 2023 21:40:47 -0700 (PDT)	[thread overview]
Message-ID: <6476cfcf.050a0220.2075.08b7@mx.google.com> (raw)
In-Reply-To: <20230531034522.375889-1-yinghsu@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 2017 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=752538

---Test result---

Test Summary:
CheckPatch                    PASS      0.79 seconds
GitLint                       PASS      0.33 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      44.90 seconds
CheckAllWarning               PASS      48.44 seconds
CheckSparse                   PASS      54.85 seconds
CheckSmatch                   PASS      148.43 seconds
BuildKernel32                 PASS      54.23 seconds
TestRunnerSetup               PASS      614.44 seconds
TestRunner_l2cap-tester       PASS      21.99 seconds
TestRunner_iso-tester         FAIL      32.58 seconds
TestRunner_bnep-tester        PASS      7.79 seconds
TestRunner_mgmt-tester        PASS      149.31 seconds
TestRunner_rfcomm-tester      PASS      12.29 seconds
TestRunner_sco-tester         PASS      11.32 seconds
TestRunner_ioctl-tester       PASS      13.46 seconds
TestRunner_mesh-tester        PASS      10.00 seconds
TestRunner_smp-tester         PASS      11.07 seconds
TestRunner_userchan-tester    PASS      7.96 seconds
IncrementalBuild              PASS      40.67 seconds

Details
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 80, Passed: 75 (93.8%), Failed: 5, Not Run: 0

Failed Test Cases
ISO AC 6(i) - Success                                Failed       0.304 seconds
ISO AC 7(i) - Success                                Failed       0.296 seconds
ISO AC 8(i) - Success                                Failed       0.308 seconds
ISO AC 9(i) - Success                                Failed       0.304 seconds
ISO AC 11(i) - Success                               Failed       0.328 seconds


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-05-31  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  3:44 [PATCH v5] Bluetooth: Fix l2cap_disconnect_req deadlock Ying Hsu
2023-05-31  4:40 ` bluez.test.bot [this message]
2023-05-31 16:28 ` Simon Horman

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=6476cfcf.050a0220.2075.08b7@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yinghsu@chromium.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.