Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, proxy-alt@proxy-alt.dev
Subject: RE: [BlueZ,v3,1/2] shared/gatt-client: verify a synthesized CCC before writing
Date: Fri, 04 Sep 2026 16:47:49 -0700 (PDT)	[thread overview]
Message-ID: <6a9b58a5.1059eef8.20e04.a017@mx.google.com> (raw)
In-Reply-To: <20260904213642.68792-1-proxy-alt@proxy-alt.dev>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.80 seconds
GitLint                       PASS      0.50 seconds
BuildEll                      PASS      13.27 seconds
BluezMake                     PASS      428.90 seconds
MakeCheck                     FAIL      6.92 seconds
MakeDistcheck                 FAIL      85.52 seconds
CheckValgrind                 FAIL      117.31 seconds
CheckSmatch                   PASS      177.18 seconds
bluezmakeextell               PASS      63.36 seconds
IncrementalBuild              PASS      439.20 seconds
ScanBuild                     PASS      559.05 seconds

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

./test-driver: line 107: 31720 Aborted                 (core dumped) "$@" > $log_file 2>&1
./test-driver: line 107: 31779 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[3]: *** [Makefile:10413: test-suite.log] Error 1
make[2]: *** [Makefile:10521: check-TESTS] Error 2
make[1]: *** [Makefile:11006: check-am] Error 2
make: *** [Makefile:11008: check] Error 2
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:

../../test-driver: line 107: 53628 Aborted                 (core dumped) "$@" > $log_file 2>&1
../../test-driver: line 107: 53908 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[4]: *** [Makefile:10413: test-suite.log] Error 1
make[3]: *** [Makefile:10521: check-TESTS] Error 2
make[2]: *** [Makefile:11006: check-am] Error 2
make[1]: *** [Makefile:11008: check] Error 2
make: *** [Makefile:10929: 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:13131:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
13131 | int main(int argc, char *argv[])
      |     ^~~~
./test-driver: line 107: 73177 Aborted                 (core dumped) "$@" > $log_file 2>&1
./test-driver: line 107: 73231 Aborted                 (core dumped) "$@" > $log_file 2>&1
make[3]: *** [Makefile:10413: test-suite.log] Error 1
make[2]: *** [Makefile:10521: check-TESTS] Error 2
make[1]: *** [Makefile:11006: check-am] Error 2
make: *** [Makefile:11008: check] Error 2


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

---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2026-09-04 23:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 18:28 [PATCH BlueZ v2] shared/gatt-client: confirm a synthesized CCC handle before writing to it Proxy alt
2026-09-04 20:13 ` [BlueZ,v2] " bluez.test.bot
2026-09-04 21:36 ` [PATCH BlueZ v3 1/2] shared/gatt-client: verify a synthesized CCC before writing Proxy alt
2026-09-04 21:36   ` [PATCH BlueZ v3 2/2] unit/test-micp: expect the FIND_INFORMATION the CCC fix adds Proxy alt
2026-09-04 23:47   ` bluez.test.bot [this message]

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=6a9b58a5.1059eef8.20e04.a017@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=proxy-alt@proxy-alt.dev \
    /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