All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, alex_lu@realsil.com.cn
Subject: RE: Bluetooth: Add more enc key size check
Date: Mon, 11 Dec 2023 00:59:34 -0800 (PST)	[thread overview]
Message-ID: <6576cf76.170a0220.a1291.0caa@mx.google.com> (raw)
In-Reply-To: <ZXbIWMZyZIYyetff@alexlu>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.52 seconds
GitLint                       PASS      0.24 seconds
SubjectPrefix                 PASS      0.19 seconds
BuildKernel                   PASS      27.94 seconds
CheckAllWarning               PASS      30.11 seconds
CheckSparse                   WARNING   36.38 seconds
CheckSmatch                   PASS      98.37 seconds
BuildKernel32                 PASS      26.50 seconds
TestRunnerSetup               PASS      425.18 seconds
TestRunner_l2cap-tester       PASS      23.09 seconds
TestRunner_iso-tester         PASS      44.69 seconds
TestRunner_bnep-tester        PASS      6.99 seconds
TestRunner_mgmt-tester        FAIL      168.41 seconds
TestRunner_rfcomm-tester      PASS      10.96 seconds
TestRunner_sco-tester         PASS      14.52 seconds
TestRunner_ioctl-tester       PASS      12.26 seconds
TestRunner_mesh-tester        PASS      8.79 seconds
TestRunner_smp-tester         PASS      10.18 seconds
TestRunner_userchan-tester    PASS      7.36 seconds
IncrementalBuild              PASS      25.61 seconds

Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/l2cap_core.c:1676:52: warning: incorrect type in assignment (different base types)net/bluetooth/l2cap_core.c:1676:52:    expected restricted __le16 [assigned] [usertype] resultnet/bluetooth/l2cap_core.c:1676:52:    got int
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 496 (99.8%), Failed: 1, Not Run: 0

Failed Test Cases
LL Privacy - Start Discovery 2 (Disable RL)          Failed       0.289 seconds


---
Regards,
Linux Bluetooth


      reply	other threads:[~2023-12-11  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  8:29 [PATCH] Bluetooth: Add more enc key size check Alex Lu
2023-12-11  8:59 ` 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=6576cf76.170a0220.a1291.0caa@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=alex_lu@realsil.com.cn \
    --cc=linux-bluetooth@vger.kernel.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.