public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Better connect debug and error reporting
Date: Tue, 01 Jul 2025 04:41:20 -0700 (PDT)	[thread overview]
Message-ID: <6863c960.170a0220.1f1e5.1bde@mx.google.com> (raw)
In-Reply-To: <20250701101520.459452-2-hadess@hadess.net>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.38 seconds
GitLint                       PENDING   0.36 seconds
BuildEll                      PASS      22.05 seconds
BluezMake                     PASS      2777.64 seconds
MakeCheck                     PASS      20.08 seconds
MakeDistcheck                 PASS      216.08 seconds
CheckValgrind                 PASS      284.01 seconds
CheckSmatch                   PASS      310.02 seconds
bluezmakeextell               PASS      133.02 seconds
IncrementalBuild              PENDING   0.32 seconds
ScanBuild                     PASS      961.27 seconds

Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:

##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:

##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  reply	other threads:[~2025-07-01 11:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 10:14 [PATCH BlueZ v4 0/8] Better connect debug and error reporting Bastien Nocera
2025-07-01 10:14 ` [PATCH BlueZ v4 1/8] error: Rename device error helper to match retval Bastien Nocera
2025-07-01 11:41   ` bluez.test.bot [this message]
2025-07-01 10:14 ` [PATCH BlueZ v4 2/8] error: Add helper to return DbusMessage errors from errno Bastien Nocera
2025-07-01 10:14 ` [PATCH BlueZ v4 3/8] device: Use new DbusMessage error helper Bastien Nocera
2025-07-01 10:14 ` [PATCH BlueZ v4 4/8] error: Make errno to string helpers private Bastien Nocera
2025-07-01 10:14 ` [PATCH BlueZ v4 5/8] device: Better error when no BR/EDR profiles can be connected to Bastien Nocera
2025-07-01 10:14 ` [PATCH BlueZ v4 6/8] device: Better "Connect" debug Bastien Nocera
2025-07-01 20:19   ` Luiz Augusto von Dentz
2025-07-01 10:14 ` [PATCH BlueZ v4 7/8] device: Better error when the link key is missing Bastien Nocera
2025-07-01 20:22   ` Luiz Augusto von Dentz
2025-07-01 10:14 ` [PATCH BlueZ v4 8/8] device: Better error when the adapter is not powered Bastien Nocera

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=6863c960.170a0220.1f1e5.1bde@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hadess@hadess.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox