From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: Add mesh testing support
Date: Wed, 31 Aug 2022 16:17:44 -0700 (PDT) [thread overview]
Message-ID: <630fec18.170a0220.c16d7.3d81@mx.google.com> (raw)
In-Reply-To: <20220831214821.274797-2-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3262 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=672980
---Test result---
Test Summary:
CheckPatch FAIL 2.87 seconds
GitLint PASS 0.96 seconds
Prep - Setup ELL PASS 31.96 seconds
Build - Prep PASS 0.66 seconds
Build - Configure PASS 10.04 seconds
Build - Make PASS 981.55 seconds
Make Check PASS 12.52 seconds
Make Check w/Valgrind PASS 347.96 seconds
Make Distcheck PASS 292.35 seconds
Build w/ext ELL - Configure PASS 10.16 seconds
Build w/ext ELL - Make PASS 101.38 seconds
Incremental Build w/ patches PASS 238.65 seconds
Scan Build PASS 784.56 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v3,2/2] tools: Add mesh-tester to test Kernel mesh support
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#362: FILE: tools/mesh-tester.c:252:
+ sizeof(set_exp_feat_param_mesh), set_exp_feat_param_mesh,
WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#502: FILE: tools/mesh-tester.c:392:
+ sizeof(set_exp_feat_param_debug), set_exp_feat_param_debug,
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#592: FILE: tools/mesh-tester.c:482:
+ test_pre_setup, test_setup, func, NULL, \
WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#593: FILE: tools/mesh-tester.c:483:
+ test_post_teardown, timeout, user, free); \
WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#728: FILE: tools/mesh-tester.c:618:
+/* Read HCI commands in the expect_hci_list and add it to the queue
+*/
ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#1040: FILE: tools/mesh-tester.c:930:
+ switch (opcode) {
+ case BT_HCI_CMD_WRITE_SCAN_ENABLE:
+ case BT_HCI_CMD_LE_SET_ADV_ENABLE:
+ case BT_HCI_CMD_LE_SET_EXT_ADV_ENABLE:
[...]
+ case BT_HCI_CMD_WRITE_SIMPLE_PAIRING_MODE:
[...]
+ default:
WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate line
#1249: FILE: tools/mesh-tester.c:1139:
+ * for a callback. */
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#1441: FILE: tools/mesh-tester.c:1331:
+ sizeof(set_exp_feat_param_mesh), set_exp_feat_param_mesh,
/github/workspace/src/12961464.patch total: 1 errors, 7 warnings, 1474 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/12961464.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.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-31 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 21:48 [PATCH BlueZ v3 0/2] Add mesh testing support Brian Gix
2022-08-31 21:48 ` [PATCH BlueZ v3 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-08-31 23:17 ` bluez.test.bot [this message]
2022-08-31 21:48 ` [PATCH BlueZ v3 2/2] tools: Add mesh-tester to test Kernel mesh support Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2022-08-31 23:59 [PATCH BlueZ v4 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-09-01 3:27 ` Add mesh testing support bluez.test.bot
2022-08-31 20:11 [PATCH BlueZ 1/2] lib: Add mgmt opcodes and events for Mesh Brian Gix
2022-08-31 21:17 ` Add mesh testing support 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=630fec18.170a0220.c16d7.3d81@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
/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.