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, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/2] shared/bass: Fix permissions not requiring encryption
Date: Wed, 01 Oct 2025 13:39:30 -0700 (PDT)	[thread overview]
Message-ID: <68dd9182.170a0220.2e7a98.2ac7@mx.google.com> (raw)
In-Reply-To: <20251001191352.77542-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PENDING   0.53 seconds
GitLint                       PENDING   0.35 seconds
BuildEll                      PASS      19.87 seconds
BluezMake                     PASS      2686.41 seconds
MakeCheck                     FAIL      20.82 seconds
MakeDistcheck                 FAIL      169.11 seconds
CheckValgrind                 FAIL      237.79 seconds
CheckSmatch                   PASS      305.16 seconds
bluezmakeextell               PASS      127.41 seconds
IncrementalBuild              PENDING   0.39 seconds
ScanBuild                     PASS      926.58 seconds

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

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

##############################
Test: MakeCheck - FAIL
Desc: Run Bluez Make Check
Output:

./test-driver: line 107: 30638 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[3]: *** [Makefile:9937: test-suite.log] Error 1
make[2]: *** [Makefile:10045: check-TESTS] Error 2
make[1]: *** [Makefile:10467: check-am] Error 2
make: *** [Makefile:10469: check] Error 2
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:

Package cups was not found in the pkg-config search path.
Perhaps you should add the directory containing `cups.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cups' found
../../test-driver: line 107: 51088 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[4]: *** [Makefile:9937: test-suite.log] Error 1
make[3]: *** [Makefile:10045: check-TESTS] Error 2
make[2]: *** [Makefile:10467: check-am] Error 2
make[1]: *** [Makefile:10469: check] Error 2
make: *** [Makefile:10390: 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:12904:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
12904 | int main(int argc, char *argv[])
      |     ^~~~
./test-driver: line 107: 69516 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[3]: *** [Makefile:9937: test-suite.log] Error 1
make[2]: *** [Makefile:10045: check-TESTS] Error 2
make[1]: *** [Makefile:10467: check-am] Error 2
make: *** [Makefile:10469: check] Error 2
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2025-10-01 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 19:13 [PATCH BlueZ v1 1/2] shared/bass: Fix permissions not requiring encryption Luiz Augusto von Dentz
2025-10-01 19:13 ` [PATCH BlueZ v1 2/2] client/player: Set QoS.Encryption if QoS.BCode is set Luiz Augusto von Dentz
2025-10-01 20:39 ` bluez.test.bot [this message]
2025-10-02 16:30 ` [PATCH BlueZ v1 1/2] shared/bass: Fix permissions not requiring encryption 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=68dd9182.170a0220.2e7a98.2ac7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox