From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yang.li@amlogic.com
Subject: RE: [v3] Bluetooth: ISO: Support SCM_TIMESTAMPING for ISO TS
Date: Thu, 03 Jul 2025 23:05:06 -0700 (PDT) [thread overview]
Message-ID: <68676f12.050a0220.291f2e.2d8e@mx.google.com> (raw)
In-Reply-To: <20250704-iso_ts-v3-1-2328bc602961@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 2027 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=978953
---Test result---
Test Summary:
CheckPatch PENDING 0.31 seconds
GitLint PENDING 0.19 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 24.26 seconds
CheckAllWarning PASS 26.77 seconds
CheckSparse PASS 30.12 seconds
BuildKernel32 PASS 24.29 seconds
TestRunnerSetup PASS 469.52 seconds
TestRunner_l2cap-tester PASS 24.87 seconds
TestRunner_iso-tester PASS 33.46 seconds
TestRunner_bnep-tester PASS 5.86 seconds
TestRunner_mgmt-tester PASS 128.74 seconds
TestRunner_rfcomm-tester PASS 9.28 seconds
TestRunner_sco-tester PASS 14.57 seconds
TestRunner_ioctl-tester PASS 9.93 seconds
TestRunner_mesh-tester FAIL 11.41 seconds
TestRunner_smp-tester PASS 8.46 seconds
TestRunner_userchan-tester PASS 6.20 seconds
IncrementalBuild PENDING 0.84 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.187 seconds
Mesh - Send cancel - 2 Timed out 1.999 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-07-04 6:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 5:36 [PATCH v3] Bluetooth: ISO: Support SCM_TIMESTAMPING for ISO TS Yang Li via B4 Relay
2025-07-04 6:05 ` bluez.test.bot [this message]
2025-07-04 8:49 ` Bastien Nocera
2025-07-07 1:35 ` Yang Li
2025-07-05 1:59 ` Jason Xing
2025-07-07 1:52 ` Yang Li
2025-07-05 20:39 ` Pauli Virtanen
2025-07-07 1:48 ` Yang Li
2025-07-07 7:41 ` Pauli Virtanen
2025-07-07 8:18 ` Yang Li
2025-07-08 15:40 ` Pauli Virtanen
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=68676f12.050a0220.291f2e.2d8e@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