From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: iso-tester: add tests for set & receive ISO HW timestamps
Date: Wed, 11 Mar 2026 10:22:58 -0700 (PDT) [thread overview]
Message-ID: <69b1a4f2.050a0220.3b4a0f.8ae3@mx.google.com> (raw)
In-Reply-To: <3c9b3d899d6e4b042e532abdb99048d1e04ff99b.1773245672.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1991 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=1065141
---Test result---
Test Summary:
CheckPatch PENDING 0.42 seconds
GitLint PENDING 0.45 seconds
BuildEll PASS 20.88 seconds
BluezMake PASS 655.27 seconds
MakeCheck PASS 18.55 seconds
MakeDistcheck PASS 246.14 seconds
CheckValgrind PASS 295.94 seconds
CheckSmatch WARNING 360.92 seconds
bluezmakeextell PASS 183.99 seconds
IncrementalBuild PENDING 0.36 seconds
ScanBuild PASS 1034.66 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/bthost.c:710:28: warning: Variable length array is used.emulator/bthost.c:711:32: warning: Variable length array is used.emulator/bthost.c:952:28: warning: Variable length array is used.emulator/bthost.c:986:28: warning: Variable length array is used.emulator/bthost.c:987:32: warning: Variable length array is used.emulator/btdev.c:482:29: warning: Variable length array is used.tools/sco-tester.c: note: in included file:./lib/bluetooth/bluetooth.h:232:15: warning: array of flexible structures./lib/bluetooth/bluetooth.h:237:31: warning: array of flexible structures
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluez/pull/1956/checks
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-11 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 16:16 [RFC PATCH BlueZ 0/4] iso-tester: add tests for set & receive ISO HW timestamps Pauli Virtanen
2026-03-11 16:16 ` [RFC PATCH BlueZ 1/4] bthost: fix receiving timestamped ISO packets Pauli Virtanen
2026-03-11 17:22 ` bluez.test.bot [this message]
2026-03-11 16:16 ` [RFC PATCH BlueZ 2/4] btdev: implement LE Read ISO TX Sync command Pauli Virtanen
2026-03-11 16:16 ` [RFC PATCH BlueZ 3/4] iso-tester: add tests for ISO HW timestamps Pauli Virtanen
2026-03-11 16:16 ` [RFC PATCH BlueZ 4/4] iso-tester: Add test for sending ISO packets with set timestamps 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=69b1a4f2.050a0220.3b4a0f.8ae3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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