All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v2,1/3] iso-tester: Add tests for GMAP broadcast QoS presets
Date: Tue, 28 Nov 2023 08:43:14 -0800 (PST)	[thread overview]
Message-ID: <656618a2.170a0220.21edc.a7a7@mx.google.com> (raw)
In-Reply-To: <20231128152832.1730901-1-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2936 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=804915

---Test result---

Test Summary:
CheckPatch                    FAIL      1.21 seconds
GitLint                       FAIL      0.84 seconds
BuildEll                      PASS      24.36 seconds
BluezMake                     PASS      583.93 seconds
MakeCheck                     PASS      11.02 seconds
MakeDistcheck                 PASS      150.40 seconds
CheckValgrind                 PASS      211.14 seconds
CheckSmatch                   WARNING   324.86 seconds
bluezmakeextell               PASS      98.70 seconds
IncrementalBuild              PASS      1588.70 seconds
ScanBuild                     PASS      952.09 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,3/3] monitor: Add proper decoding of TLV for BASE
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#100: 
              Codec Specific Configuration: Location: Front Left (0x00000001)

/github/workspace/src/src/13471360.patch total: 0 errors, 1 warnings, 116 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/src/13471360.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.


##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,3/3] monitor: Add proper decoding of TLV for BASE

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
26: B3 Line contains hard tab characters (\t): "            Metadata: Context	Conversational (0x0002)"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1860:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3606:52: warning: array of flexible structuresmonitor/bt.h:3594:40: warning: array of flexible structures


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-11-28 16:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 15:28 [PATCH BlueZ v2 1/3] iso-tester: Add tests for GMAP broadcast QoS presets Luiz Augusto von Dentz
2023-11-28 15:28 ` [PATCH BlueZ v2 2/3] util: Make debugger arg of util_debug_ltv const Luiz Augusto von Dentz
2023-11-28 15:28 ` [PATCH BlueZ v2 3/3] monitor: Add proper decoding of TLV for BASE Luiz Augusto von Dentz
2023-11-28 16:43 ` bluez.test.bot [this message]
2023-11-28 17:40 ` [PATCH BlueZ v2 1/3] iso-tester: Add tests for GMAP broadcast QoS presets 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=656618a2.170a0220.21edc.a7a7@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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 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.