From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v1] Bluetooth: hci_event: Fix not using key encryption size when its known
Date: Wed, 30 Apr 2025 12:55:14 -0700 (PDT) [thread overview]
Message-ID: <68128022.170a0220.f31d7.bd1f@mx.google.com> (raw)
In-Reply-To: <20250430192448.2386611-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2716 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=958631
---Test result---
Test Summary:
CheckPatch PENDING 0.42 seconds
GitLint PENDING 0.32 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 24.64 seconds
CheckAllWarning PASS 27.08 seconds
CheckSparse WARNING 30.35 seconds
BuildKernel32 PASS 24.21 seconds
TestRunnerSetup PASS 459.85 seconds
TestRunner_l2cap-tester PASS 22.59 seconds
TestRunner_iso-tester PASS 33.28 seconds
TestRunner_bnep-tester PASS 4.95 seconds
TestRunner_mgmt-tester FAIL 120.63 seconds
TestRunner_rfcomm-tester PASS 7.83 seconds
TestRunner_sco-tester PASS 13.14 seconds
TestRunner_ioctl-tester PASS 8.27 seconds
TestRunner_mesh-tester FAIL 7.15 seconds
TestRunner_smp-tester PASS 7.21 seconds
TestRunner_userchan-tester PASS 4.97 seconds
IncrementalBuild PENDING 0.71 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
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: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 490, Passed: 483 (98.6%), Failed: 3, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 2 (2 Devices to AL) Failed 0.169 seconds
LL Privacy - Add Device 3 (AL is full) Failed 0.193 seconds
LL Privacy - Set Device Flag 1 (Device Privacy) Failed 0.154 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in run_timer_softirq+0x76f/0x7d0
WARNING: CPU: 0 PID: 36 at kernel/workqueue.c:2257 __queue_work+0x93e/0xba0
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.115 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-04-30 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 19:24 [PATCH v1] Bluetooth: hci_event: Fix not using key encryption size when its known Luiz Augusto von Dentz
2025-04-30 19:55 ` bluez.test.bot [this message]
2025-05-01 6:05 ` Paul Menzel
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=68128022.170a0220.f31d7.bd1f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox