From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yang.li@amlogic.com
Subject: RE: iso: add BT_ISO_TS optional to enable ISO timestamp
Date: Mon, 28 Apr 2025 21:35:19 -0700 (PDT) [thread overview]
Message-ID: <68105707.630a0220.1ee2d8.2c02@mx.google.com> (raw)
In-Reply-To: <20250429-iso_ts-v1-1-e586f30de6cb@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 2863 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=957927
---Test result---
Test Summary:
CheckPatch PENDING 0.35 seconds
GitLint PENDING 0.28 seconds
SubjectPrefix FAIL 0.41 seconds
BuildKernel PASS 24.31 seconds
CheckAllWarning PASS 26.61 seconds
CheckSparse WARNING 30.08 seconds
BuildKernel32 PASS 24.09 seconds
TestRunnerSetup PASS 456.46 seconds
TestRunner_l2cap-tester PASS 22.11 seconds
TestRunner_iso-tester FAIL 35.46 seconds
TestRunner_bnep-tester PASS 4.65 seconds
TestRunner_mgmt-tester PASS 118.65 seconds
TestRunner_rfcomm-tester PASS 7.84 seconds
TestRunner_sco-tester PASS 12.86 seconds
TestRunner_ioctl-tester PASS 8.19 seconds
TestRunner_mesh-tester FAIL 6.07 seconds
TestRunner_smp-tester PASS 7.27 seconds
TestRunner_userchan-tester PASS 4.90 seconds
IncrementalBuild PENDING 0.55 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/iso.c:2330:42: warning: restricted __le16 degrades to integer
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 127, Passed: 124 (97.6%), Failed: 2, Not Run: 1
Failed Test Cases
ISO Send - TX Timestamping Failed 0.192 seconds
ISO Send - TX CMSG Timestamping Failed 0.185 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: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.120 seconds
Mesh - Send cancel - 2 Failed 0.141 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-29 4:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 3:35 [PATCH] iso: add BT_ISO_TS optional to enable ISO timestamp Yang Li via B4 Relay
2025-04-29 4:35 ` bluez.test.bot [this message]
2025-04-29 14:26 ` Pauli Virtanen
2025-04-29 14:29 ` Pauli Virtanen
2025-04-29 14:31 ` Luiz Augusto von Dentz
2025-04-29 14:35 ` Pauli Virtanen
2025-04-29 14:38 ` Luiz Augusto von Dentz
2025-04-30 7:45 ` Yang Li
2025-04-29 14:30 ` Luiz Augusto von Dentz
2025-05-07 6:19 ` kernel test robot
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=68105707.630a0220.1ee2d8.2c02@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox