Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ] tester.config: add missing CRYPTO_AES
Date: Sun, 17 May 2026 15:05:28 -0700 (PDT)	[thread overview]
Message-ID: <6a0a3ba8.09f534dc.1da071.8352@mx.google.com> (raw)
In-Reply-To: <478a4d370bc0b20b98223507166dfd580ae8477d.1779051031.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.40 seconds
GitLint                       FAIL      0.30 seconds
BuildEll                      PASS      20.76 seconds
BluezMake                     PASS      658.47 seconds
MakeCheck                     FAIL      18.44 seconds
MakeDistcheck                 FAIL      228.35 seconds
CheckValgrind                 FAIL      293.09 seconds
CheckSmatch                   PASS      350.33 seconds
bluezmakeextell               PASS      182.08 seconds
IncrementalBuild              PASS      645.34 seconds
ScanBuild                     PASS      1018.26 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ] tester.config: add missing CRYPTO_AES
WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '4a1507625b0', maybe rebased or not pulled?
#81: 
Kernel commit 4a1507625b0 ("Bluetooth: SMP: Use AES-CMAC library

/github/workspace/src/patch/14577648.patch total: 0 errors, 1 warnings, 21 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/14577648.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] tester.config: add missing CRYPTO_AES

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: B2 Line has trailing whitespace: "    "
28: B2 Line has trailing whitespace: "    "
30: B2 Line has trailing whitespace: "    "
31: B1 Line exceeds max length (115>80): "    https://github.com/bluez/bluetooth-next/commit/84ebde6f819c06cc1d804a471d9fb60b7986e190/checks/76408920221/logs"
32: B2 Line has trailing whitespace: "    "
33: B1 Line exceeds max length (115>80): "    https://github.com/bluez/bluetooth-next/commit/82f0e0c7d08eb21d0579471a3b5c004cf95dda08/checks/75862464065/logs"
##############################
Test: MakeCheck - FAIL
Desc: Run Bluez Make Check
Output:

make[3]: *** [Makefile:10239: test-suite.log] Error 1
make[2]: *** [Makefile:10347: check-TESTS] Error 2
make[1]: *** [Makefile:10818: check-am] Error 2
make: *** [Makefile:10820: check] Error 2
##############################
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
##############################
Test: CheckValgrind - FAIL
Desc: Run Bluez Make Check with Valgrind
Output:

tools/mgmt-tester.c: In function ‘main’:
tools/mgmt-tester.c:12990:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
12990 | int main(int argc, char *argv[])
      |     ^~~~
make[3]: *** [Makefile:10239: test-suite.log] Error 1
make[2]: *** [Makefile:10347: check-TESTS] Error 2
make[1]: *** [Makefile:10818: check-am] Error 2
make: *** [Makefile:10820: check] Error 2


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-05-17 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-17 20:51 [PATCH BlueZ] tester.config: add missing CRYPTO_AES Pauli Virtanen
2026-05-17 22:05 ` bluez.test.bot [this message]
2026-05-21 13:30 ` 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=6a0a3ba8.09f534dc.1da071.8352@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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