Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, prathibha.madugonde@oss.qualcomm.com
Subject: RE: [BlueZ,v2] shared/rap: Add client ranging registration and notification parsing
Date: Thu, 21 May 2026 02:42:28 -0700 (PDT)	[thread overview]
Message-ID: <6a0ed384.87685153.2b70a7.9766@mx.google.com> (raw)
In-Reply-To: <20260521071821.2355923-1-prathm@qti.qualcomm.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.01 seconds
GitLint                       PASS      0.34 seconds
BuildEll                      PASS      20.39 seconds
BluezMake                     PASS      609.40 seconds
MakeCheck                     PASS      1.18 seconds
MakeDistcheck                 FAIL      215.51 seconds
CheckValgrind                 PASS      200.78 seconds
CheckSmatch                   PASS      322.84 seconds
bluezmakeextell               PASS      164.82 seconds
IncrementalBuild              PASS      606.23 seconds
ScanBuild                     PASS      942.07 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2] shared/rap: Add client ranging registration and notification parsing
WARNING:TYPO_SPELLING: 'fuctions' may be misspelled - perhaps 'functions'?
#161: 
Use helper fuctions for readablitiy and code indentation.
           ^^^^^^^^

/github/workspace/src/patch/14585921.patch total: 0 errors, 1 warnings, 935 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/patch/14585921.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: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:

make[4]: *** [Makefile:10239: test-suite.log] Error 1
make[3]: *** [Makefile:10347: check-TESTS] Error 2
make[2]: *** [Makefile:10818: check-am] Error 2
make[1]: *** [Makefile:10820: check] Error 2
make: *** [Makefile:10741: distcheck] Error 1


https://github.com/bluez/bluez/pull/2141

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-05-21  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  7:18 [PATCH BlueZ v2] shared/rap: Add client ranging registration and notification parsing Prathibha Madugonde
2026-05-21  9:42 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-21 10:32 Prathibha Madugonde
2026-05-21 12:47 ` [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=6a0ed384.87685153.2b70a7.9766@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=prathibha.madugonde@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox