All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v1] Bluetooth: hci_event: Fix not indicating new connection for BIG Sync
Date: Wed, 31 Jan 2024 08:58:20 -0800 (PST)	[thread overview]
Message-ID: <65ba7c2c.e90a0220.94fcb.7357@mx.google.com> (raw)
In-Reply-To: <20240131162825.826774-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.80 seconds
GitLint                       PASS      0.33 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      27.89 seconds
CheckAllWarning               PASS      30.81 seconds
CheckSparse                   WARNING   35.76 seconds
CheckSmatch                   WARNING   99.14 seconds
BuildKernel32                 PASS      27.12 seconds
TestRunnerSetup               PASS      433.23 seconds
TestRunner_l2cap-tester       PASS      22.89 seconds
TestRunner_iso-tester         PASS      42.58 seconds
TestRunner_bnep-tester        PASS      6.84 seconds
TestRunner_mgmt-tester        FAIL      227.13 seconds
TestRunner_rfcomm-tester      PASS      10.74 seconds
TestRunner_sco-tester         PASS      14.33 seconds
TestRunner_ioctl-tester       FAIL      17.16 seconds
TestRunner_mesh-tester        PASS      8.62 seconds
TestRunner_smp-tester         PASS      9.64 seconds
TestRunner_userchan-tester    PASS      7.22 seconds
IncrementalBuild              PASS      26.25 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 485 (97.6%), Failed: 11, Not Run: 1

Failed Test Cases
Get Clock Info - Success                             Timed out    2.354 seconds
Get Conn Info - Success                              Timed out    1.838 seconds
Get Conn Info - Power off                            Timed out    1.822 seconds
Adv. connectable & connected (peripheral) - Success  Timed out   10.770 seconds
Adv. non-connectable & connected (peripheral) - Success Timed out    9.992 seconds
Adv. connectable & connected (central) - Success     Timed out    9.996 seconds
Adv. non-connectable & connected (central) - Success Timed out    9.993 seconds
Ext Adv. connectable & connected (peripheral)        Timed out   10.618 seconds
Ext Adv. non-connectable & connected (peripheral)    Timed out   10.000 seconds
Ext Adv. connectable & connected (central)           Timed out    9.994 seconds
Ext Adv. non-connectable & connected (central)       Timed out   10.003 seconds
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
Total: 28, Passed: 25 (89.3%), Failed: 3, Not Run: 0

Failed Test Cases
Connection List                                      Timed out    1.905 seconds
Connection Info                                      Timed out    1.991 seconds
Authentication Info                                  Timed out    2.512 seconds


---
Regards,
Linux Bluetooth


      reply	other threads:[~2024-01-31 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 16:28 [PATCH v1] Bluetooth: hci_event: Fix not indicating new connection for BIG Sync Luiz Augusto von Dentz
2024-01-31 16:58 ` 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=65ba7c2c.e90a0220.94fcb.7357@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 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.