From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: [bluez] tools/test-runner: Fix TESTHOME parsing for short paths
Date: Thu, 19 Nov 2026 10:31:59 -0800 (PST) [thread overview]
Message-ID: <6aff409f.b3f5340a.30e815.e879@mx.google.com> (raw)
In-Reply-To: <20261119-fix_test_runner-v1-1-ddad300e86ed@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1482 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/series/1216093/
---Test result---
Test Summary:
CheckPatch PASS 0.47 seconds
GitLint FAIL 0.33 seconds
BuildEll PASS 16.29 seconds
BluezMake PASS 234.11 seconds
CheckSmatch PASS 238.04 seconds
bluezmakeextell PASS 76.95 seconds
TestFunctional PASS 1030.11 seconds
IncrementalBuild PASS 238.70 seconds
ScanBuild WARNING 856.96 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[bluez] tools/test-runner: Fix TESTHOME parsing for short paths
20: B2 Line has trailing whitespace: "-- "
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
tools/btgatt-server.c:1204:2: warning: Value stored to 'argv' is never read [deadcode.DeadStores]
tools/btgatt-client.c:1822:2: warning: Value stored to 'argv' is never read [deadcode.DeadStores]
1204 | argv -= optind;
1822 | argv += optind;
| ^ ~~~~~~
| ^ ~~~~~~
1 warning generated.
https://github.com/bluez/bluez/pull/2851
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-19 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 12:09 [PATCH bluez] tools/test-runner: Fix TESTHOME parsing for short paths Zijun Hu
2026-11-19 18:31 ` 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=6aff409f.b3f5340a.30e815.e879@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zijun.hu@oss.qualcomm.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