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, kupper.benedek@gmail.com
Subject: RE: [BlueZ] gatt-client: allow AcquireNotify when characteristic has indicate flag
Date: Thu, 22 Aug 2024 06:03:17 -0700 (PDT)	[thread overview]
Message-ID: <66c73715.050a0220.1226a.21a8@mx.google.com> (raw)
In-Reply-To: <20240822113226.223790-1-kupper.benedek@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.46 seconds
GitLint                       PASS      0.32 seconds
BuildEll                      PASS      24.50 seconds
BluezMake                     PASS      1685.40 seconds
MakeCheck                     FAIL      13.82 seconds
MakeDistcheck                 FAIL      159.20 seconds
CheckValgrind                 FAIL      251.10 seconds
CheckSmatch                   PASS      353.95 seconds
bluezmakeextell               PASS      119.71 seconds
IncrementalBuild              PASS      1440.61 seconds
ScanBuild                     PASS      1031.19 seconds

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

make[3]: *** [Makefile:11766: test-suite.log] Error 1
make[2]: *** [Makefile:11874: check-TESTS] Error 2
make[1]: *** [Makefile:12303: check-am] Error 2
make: *** [Makefile:12305: 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
make[4]: *** [Makefile:11766: test-suite.log] Error 1
make[3]: *** [Makefile:11874: check-TESTS] Error 2
make[2]: *** [Makefile:12303: check-am] Error 2
make[1]: *** [Makefile:12305: check] Error 2
make: *** [Makefile:12226: 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:12725:5: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
12725 | int main(int argc, char *argv[])
      |     ^~~~
make[3]: *** [Makefile:11766: test-suite.log] Error 1
make[2]: *** [Makefile:11874: check-TESTS] Error 2
make[1]: *** [Makefile:12303: check-am] Error 2
make: *** [Makefile:12305: check] Error 2


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-08-22 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 11:32 [PATCH BlueZ] gatt-client: allow AcquireNotify when characteristic has indicate flag Benedek Kupper
2024-08-22 13:03 ` bluez.test.bot [this message]
2024-08-22 16:17 ` Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2024-08-22  9:46 Benedek Kupper
2024-08-22 10:16 ` [BlueZ] " 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=66c73715.050a0220.1226a.21a8@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=kupper.benedek@gmail.com \
    --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