All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yang.li@amlogic.com
Subject: RE: Bluetooth: Prevent unintended pause by checking if advertising is active
Date: Mon, 16 Jun 2025 04:32:51 -0700 (PDT)	[thread overview]
Message-ID: <685000e3.050a0220.2cab6c.2269@mx.google.com> (raw)
In-Reply-To: <20250616-bluetooth_adv-v1-1-6876bf4e85b4@amlogic.com>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.27 seconds
GitLint                       PENDING   0.22 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      24.99 seconds
CheckAllWarning               PASS      27.37 seconds
CheckSparse                   PASS      30.84 seconds
BuildKernel32                 PASS      25.07 seconds
TestRunnerSetup               PASS      471.95 seconds
TestRunner_l2cap-tester       PASS      25.80 seconds
TestRunner_iso-tester         FAIL      8.01 seconds
TestRunner_bnep-tester        PASS      6.00 seconds
TestRunner_mgmt-tester        FAIL      135.31 seconds
TestRunner_rfcomm-tester      PASS      9.67 seconds
TestRunner_sco-tester         PASS      15.09 seconds
TestRunner_ioctl-tester       PASS      10.30 seconds
TestRunner_mesh-tester        PASS      7.47 seconds
TestRunner_smp-tester         PASS      8.66 seconds
TestRunner_userchan-tester    PASS      6.38 seconds
IncrementalBuild              PENDING   0.44 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 480 (98.0%), Failed: 6, Not Run: 4

Failed Test Cases
LL Privacy - Add Device 4 (Disable Adv)              Timed out    1.882 seconds
LL Privacy - Set Flags 5 (Multi Adv)                 Timed out    2.149 seconds
LL Privacy - Set Flags 6 (Multi Dev and Multi Adv)   Timed out    2.006 seconds
LL Privacy - Remove Device 4 (Disable Adv)           Timed out    2.231 seconds
LL Privacy - Remove Device 5 (Multi Adv)             Timed out    1.986 seconds
LL Privacy - Set Device Flag 1 (Device Privacy)      Failed       0.174 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  reply	other threads:[~2025-06-16 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 11:05 [PATCH] Bluetooth: Prevent unintended pause by checking if advertising is active Yang Li
2025-06-16 11:05 ` Yang Li via B4 Relay
2025-06-16 11:32 ` bluez.test.bot [this message]
2025-06-18 13:06 ` Luiz Augusto von Dentz
2025-06-19  2:50   ` Yang Li

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=685000e3.050a0220.2cab6c.2269@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yang.li@amlogic.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.