From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: unit: Introduce test-bass
Date: Mon, 29 May 2023 03:39:35 -0700 (PDT) [thread overview]
Message-ID: <647480e7.170a0220.f1373.f64d@mx.google.com> (raw)
In-Reply-To: <20230529084650.72126-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2061 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=751789
---Test result---
Test Summary:
CheckPatch PASS 1.06 seconds
GitLint FAIL 0.81 seconds
BuildEll PASS 30.00 seconds
BluezMake PASS 1050.56 seconds
MakeCheck PASS 12.23 seconds
MakeDistcheck PASS 173.29 seconds
CheckValgrind PASS 277.57 seconds
CheckSmatch PASS 391.37 seconds
bluezmakeextell PASS 116.06 seconds
IncrementalBuild PASS 1826.44 seconds
ScanBuild PASS 1214.80 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,1/2] shared/bass: Add Write Without Response property to the CP characteristic
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
1: T1 Title exceeds max length (85>80): "[BlueZ,1/2] shared/bass: Add Write Without Response property to the CP characteristic"
[BlueZ,2/2] unit: Introduce test-bass
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
6: B2 Line has trailing whitespace: "Test Summary "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-29 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 8:46 [PATCH BlueZ 0/2] unit: Introduce test-bass Iulia Tanasescu
2023-05-29 8:46 ` [PATCH BlueZ 1/2] shared/bass: Add Write Without Response property to the CP characteristic Iulia Tanasescu
2023-05-29 10:39 ` bluez.test.bot [this message]
2023-05-29 8:46 ` [PATCH BlueZ 2/2] unit: Introduce test-bass Iulia Tanasescu
2023-05-30 23:20 ` [PATCH BlueZ 0/2] " patchwork-bot+bluetooth
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=647480e7.170a0220.f1373.f64d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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.