public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, neeraj.sanjaykale@nxp.com
Subject: RE: Bluetooth: btnxpuart: Update firmware names
Date: Fri, 14 Jun 2024 02:35:25 -0700 (PDT)	[thread overview]
Message-ID: <666c0edd.050a0220.4a944.464e@mx.google.com> (raw)
In-Reply-To: <20240614084941.6832-2-neeraj.sanjaykale@nxp.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.81 seconds
GitLint                       PASS      0.65 seconds
SubjectPrefix                 FAIL      0.50 seconds
BuildKernel                   PASS      29.42 seconds
CheckAllWarning               PASS      32.42 seconds
CheckSparse                   PASS      37.90 seconds
CheckSmatch                   PASS      109.66 seconds
BuildKernel32                 PASS      28.65 seconds
TestRunnerSetup               PASS      529.34 seconds
TestRunner_l2cap-tester       PASS      18.91 seconds
TestRunner_iso-tester         PASS      33.54 seconds
TestRunner_bnep-tester        PASS      4.97 seconds
TestRunner_mgmt-tester        FAIL      115.22 seconds
TestRunner_rfcomm-tester      PASS      7.70 seconds
TestRunner_sco-tester         PASS      15.43 seconds
TestRunner_ioctl-tester       PASS      8.29 seconds
TestRunner_mesh-tester        PASS      6.08 seconds
TestRunner_smp-tester         PASS      7.03 seconds
TestRunner_userchan-tester    PASS      5.53 seconds
IncrementalBuild              PASS      34.24 seconds

Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 492, Passed: 488 (99.2%), Failed: 2, Not Run: 2

Failed Test Cases
LL Privacy - Add Device 4 (2 Devices to AL)          Failed       0.162 seconds
LL Privacy - Add Device 6 (RL is full)               Failed       0.198 seconds


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-06-14  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-14  8:49 [PATCH v4 0/2] Bluetooth: btnxpuart: Update firmware names Neeraj Sanjay Kale
2024-06-14  8:49 ` [PATCH v4 1/2] dt-bindings: net: bluetooth: nxp: Add firmware-name property Neeraj Sanjay Kale
2024-06-14  9:35   ` bluez.test.bot [this message]
2024-06-14  8:49 ` [PATCH v4 2/2] Bluetooth: btnxpuart: Update firmware names Neeraj Sanjay Kale
2024-06-14 17:00 ` [PATCH v4 0/2] " patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2024-05-29  9:53 [PATCH v3 1/2] dt-bindings: net: bluetooth: nxp: Add firmware-name property Neeraj Sanjay Kale
2024-05-29 10:14 ` Bluetooth: btnxpuart: Update firmware names bluez.test.bot
2024-05-14  9:13 [PATCH v3 1/2] dt-bindings: net: bluetooth: nxp: Add firmware-name property Neeraj Sanjay Kale
2024-05-14  9:56 ` Bluetooth: btnxpuart: Update firmware names bluez.test.bot
2024-04-10  8:10 [PATCH v3 1/2] dt-bindings: net: bluetooth: nxp: Add firmware-name property Neeraj Sanjay Kale
2024-04-10  8:36 ` Bluetooth: btnxpuart: Update firmware names bluez.test.bot
2024-04-08 13:22 [PATCH v2 1/2] dt-bindings: net: bluetooth: btnxpuart: Add firmware-name property Neeraj Sanjay Kale
2024-04-08 13:56 ` Bluetooth: btnxpuart: Update firmware names bluez.test.bot
2024-04-05  9:01 [PATCH v1 1/2] dt-bindings: net: bluetooth: btnxpuart: Add firmware-name property Neeraj Sanjay Kale
2024-04-05  9:32 ` Bluetooth: btnxpuart: Update firmware names bluez.test.bot

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=666c0edd.050a0220.4a944.464e@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=neeraj.sanjaykale@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox