From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Functional/integration testing
Date: Sat, 13 Jun 2026 10:09:55 -0700 (PDT) [thread overview]
Message-ID: <6a2d8ee3.396644cf.3045c0.f16b@mx.google.com> (raw)
In-Reply-To: <476910717b76052dd8d3673b92b00bc9c628b349.1781365708.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1990 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=1111076
---Test result---
Test Summary:
CheckPatch FAIL 2.09 seconds
GitLint PASS 1.46 seconds
BuildEll PASS 21.37 seconds
BluezMake PASS 624.17 seconds
MakeCheck PASS 19.31 seconds
MakeDistcheck PASS 238.73 seconds
CheckValgrind PASS 276.72 seconds
CheckSmatch PASS 328.01 seconds
bluezmakeextell PASS 167.45 seconds
IncrementalBuild PASS 644.71 seconds
ScanBuild PASS 973.07 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v6,2/6] test: add functional/integration testing framework
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#422: FILE: test/test-functional
ERROR:EXECUTE_PERMISSIONS: do not set execute permissions for source files
#449: FILE: test/test-functional-attach
/github/workspace/src/patch/14627534.patch total: 2 errors, 0 warnings, 279 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/patch/14627534.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
https://github.com/bluez/bluez/pull/2228
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-06-13 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 15:48 [PATCH BlueZ v6 0/6] Functional/integration testing Pauli Virtanen
2026-06-13 15:48 ` [PATCH BlueZ v6 1/6] doc: add functional/integration testing documentation Pauli Virtanen
2026-06-13 17:09 ` bluez.test.bot [this message]
2026-06-13 15:48 ` [PATCH BlueZ v6 2/6] test: add functional/integration testing framework Pauli Virtanen
2026-06-13 15:48 ` [PATCH BlueZ v6 3/6] build: add functional testing target Pauli Virtanen
2026-06-13 15:48 ` [PATCH BlueZ v6 4/6] test: functional: impose Python code formatting Pauli Virtanen
2026-06-13 15:48 ` [PATCH BlueZ v6 5/6] test: functional: add some Agent1 interface tests Pauli Virtanen
2026-06-13 15:48 ` [PATCH BlueZ v6 6/6] test: functional: add basic obex file transfer tests Pauli Virtanen
-- strict thread matches above, loose matches on Subject: below --
2026-05-13 16:17 [PATCH BlueZ v5 01/16] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-05-13 18:23 ` Functional/integration testing bluez.test.bot
2026-04-05 12:39 [PATCH BlueZ v4 01/20] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-04-05 14:24 ` Functional/integration testing bluez.test.bot
2026-03-22 21:29 [PATCH BlueZ v3 01/20] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-03-22 22:38 ` Functional/integration testing bluez.test.bot
2026-03-20 21:10 [PATCH BlueZ v2 01/20] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-03-20 22:14 ` Functional/integration testing bluez.test.bot
2026-02-28 12:51 [PATCH BlueZ 01/11] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-02-28 13:45 ` Functional/integration testing bluez.test.bot
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=6a2d8ee3.396644cf.3045c0.f16b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.