All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, r.smirnov@omp.ru
Subject: RE: [BlueZ,v2] client/player: add error code handling to transport_recv()
Date: Thu, 04 Jul 2024 02:52:23 -0700 (PDT)	[thread overview]
Message-ID: <668670d7.050a0220.36da7.8ff4@mx.google.com> (raw)
In-Reply-To: <20240704074759.15844-1-r.smirnov@omp.ru>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.45 seconds
GitLint                       FAIL      0.49 seconds
BuildEll                      PASS      25.33 seconds
BluezMake                     PASS      1897.59 seconds
MakeCheck                     PASS      13.34 seconds
MakeDistcheck                 PASS      180.67 seconds
CheckValgrind                 PASS      253.61 seconds
CheckSmatch                   PASS      359.52 seconds
bluezmakeextell               PASS      127.39 seconds
IncrementalBuild              PASS      1666.22 seconds
ScanBuild                     PASS      1035.74 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2] client/player: add error code handling to transport_recv()

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
7: B2 Line has trailing whitespace: " V1 -> V2: the name of the patch has been shortened "


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-07-04  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  7:47 [PATCH BlueZ v2] client/player: add error code handling to transport_recv() Roman Smirnov
2024-07-04  9:52 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-04 10:49 Roman Smirnov
2024-07-04 12:41 ` [BlueZ,v2] " 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=668670d7.050a0220.36da7.8ff4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=r.smirnov@omp.ru \
    /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.