All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, nicoyip.dev@gmail.com
Subject: RE: [v5] Bluetooth: hci_sync: wait for directed advertising completion
Date: Mon, 24 Aug 2026 07:33:41 -0700 (PDT)	[thread overview]
Message-ID: <6a8c5645.3f2ee557.13dbd1.7444@mx.google.com> (raw)
In-Reply-To: <20260824134149.212607-1-nicoyip.dev@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.14 seconds
VerifyFixes                   PASS      0.07 seconds
VerifySignedoff               PASS      0.07 seconds
GitLint                       PASS      0.20 seconds
SubjectPrefix                 PASS      0.06 seconds
BuildKernel                   PASS      24.41 seconds
CheckAllWarning               PASS      27.42 seconds
CheckSparse                   PASS      24.44 seconds
BuildKernel32                 PASS      28.23 seconds
CheckKernelLLVM               SKIP      0.00 seconds
TestRunnerSetup               PASS      427.64 seconds
TestRunner_l2cap-tester       PASS      62.80 seconds
TestRunner_iso-tester         FAIL      92.02 seconds
TestRunner_bnep-tester        PASS      17.87 seconds
TestRunner_mgmt-tester        FAIL      206.09 seconds
TestRunner_rfcomm-tester      PASS      23.10 seconds
TestRunner_sco-tester         PASS      27.28 seconds
TestRunner_ioctl-tester       PASS      23.03 seconds
TestRunner_mesh-tester        FAIL      23.68 seconds
TestRunner_smp-tester         PASS      21.01 seconds
TestRunner_userchan-tester    PASS      18.25 seconds
TestRunner_6lowpan-tester     PASS      21.11 seconds
IncrementalBuild              PASS      22.13 seconds

Details
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 141, Passed: 136 (96.5%), Failed: 5, Not Run: 0

Failed Test Cases
ISO Broadcaster PAST Info - Success                  Timed out    2.680 seconds
ISO Broadcaster PAST Info RPA - Success              Timed out    1.987 seconds
ISO Broadcaster PAST Sender - Success                Timed out    2.006 seconds
ISO Broadcaster PAST Receiver - Success              Timed out    2.811 seconds
ISO Broadcaster PAST Receiver Sync Lost - Success    Timed out    2.525 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 496 (99.0%), Failed: 1, Not Run: 4

Failed Test Cases
Read Exp Feature - Success                           Failed       0.236 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0

Failed Test Cases
Mesh - Send cancel - 1                               Timed out    2.545 seconds
Mesh - Send cancel - 2                               Timed out    1.992 seconds


https://github.com/bluez/bluetooth-next/pull/644

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-08-24 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:41 [PATCH v5] Bluetooth: hci_sync: wait for directed advertising completion Chengfeng Ye
2026-08-24 14:33 ` bluez.test.bot [this message]

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=6a8c5645.3f2ee557.13dbd1.7444@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=nicoyip.dev@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 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.