All of lore.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: Add HID over GATT functional tests
Date: Thu, 24 Sep 2026 12:16:00 -0700 (PDT)	[thread overview]
Message-ID: <6ab576f0.0c0d0188.361926.08e3@mx.google.com> (raw)
In-Reply-To: <20260924154631.369299-2-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 7064 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/series/1173252/

---Test result---

Test Summary:
CheckPatch                    PASS      3.54 seconds
GitLint                       FAIL      2.94 seconds
BuildEll                      PASS      16.88 seconds
BluezMake                     PASS      230.92 seconds
MakeCheck                     PASS      12.88 seconds
MakeDistcheck                 PASS      105.89 seconds
CheckValgrind                 PASS      160.51 seconds
CheckSmatch                   PASS      166.27 seconds
bluezmakeextell               PASS      64.61 seconds
TestFunctional                FAIL      815.22 seconds
IncrementalBuild              PASS      266.83 seconds
ScanBuild                     PASS      657.94 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v3,1/9] shared/gatt-client: Fix calling destroy after unregistering notify

1: T1 Title exceeds max length (81>80): "[BlueZ,v3,1/9] shared/gatt-client: Fix calling destroy after unregistering notify"
[BlueZ,v3,2/9] attrib: Fix unregistering notifications registered with bt_gatt_client

1: T1 Title exceeds max length (85>80): "[BlueZ,v3,2/9] attrib: Fix unregistering notifications registered with bt_gatt_client"
##############################
Test: TestFunctional - FAIL
Desc: Run test-functional
Output:
FAIL functional.test_bap::test_bap_unicast_set_transport_created[hosts9-vm3-legacy]: failed on setup with "pytest_bluezenv.rpc.RemoteError: [Errno 32] Broken pipe
    Remote traceback:
        Traceback (most recent call last):
          File "/usr/local/lib/python3.14/dist-packages/pytest_bluezenv/../pytest_bluezenv/rpc.py", line 102, in server_stream
            result = method(*msg["a"], **msg["kw"])
          File "/usr/local/lib/python3.14/dist-packages/pytest_bluezenv/../pytest_bluezenv/env.py", line 256, in call_plugin
            return getattr(self.plugins[name], method)(*a, **kw)
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
          File "/usr/local/lib/python3.14/dist-packages/pytest_bluezenv/../pytest_bluezenv/host_plugins.py", line 447, in send
            return ctl.send(*a, **kw)
                   ~~~~~~~~^^^^^^^^^^
          File "/usr/lib/python3/dist-packages/pexpect/popen_spawn.py", line 142, in send
            return self.proc.stdin.write(b)
                   ~~~~~~~~~~~~~~~~~~~~~^^^
        BrokenPipeError: [Errno 32] Broken pipe"
FAIL functional.test_bap::test_bap_unicast_set_transport_created[hosts9-vm3-legacy]: failed on teardown with "pytest_bluezenv.plugin.CoredumpWarning: Core dump: test-bluezenv-hosts9.2-bluetoothctl-1790276391-121.core
        /usr/bin/gdb: warning: Couldn't determine a path for the index cache directory.
        [New LWP 121]
        [Thread debugging using libthread_db enabled]
        Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
        Core was generated by `/home/runner/work/bluez/bluez/src/src/client/bluetoothctl -a auto:NoInputNoOutput --init-script /home/runner/work/bluez/bluez/src/src/test/../client/scripts/bap-sink-lc3-right.bt'.
        Program terminated with signal SIGABRT, Aborted.
        #0  __pthread_kill_implementation (threadid=<optimized out>, signo=6, no_tid=0) at ./nptl/pthread_kill.c:44

        warning: 44	./nptl/pthread_kill.c: No such file or directory

        Thread 1 (Thread 0x7f3293a9ed40 (LWP 121)):
        #0  __pthread_kill_implementation (threadid=<optimized out>, signo=6, no_tid=0) at ./nptl/pthread_kill.c:44
                tid = <optimized out>
                ret = 0
                pd = <optimized out>
                old_mask = {__val = {140726025679776}}
                ret = <optimized out>
        #1  __pthread_kill_internal (threadid=<optimized out>, signo=6) at ./nptl/pthread_kill.c:89
        No locals.
        #2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:100
        No locals.
        #3  0x00007f32940ddb7e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
                ret = <optimized out>
        #4  0x00007f32940c08ec in __GI_abort () at ./stdlib/abort.c:77
                act = {__sigaction_handler = {sa_handler = 0x7ba292ee1520, sa_sigaction = 0x7ba292ee1520}, sa_mask = {__val = {139855210919203, 140726025679792, 139855209372592, 7791336406271877491, 139855210919072, 140726025679872, 139855220451473, 139855221501984, 139855201496144, 0, 139855210919072, 4294967295, 139855208120320, 140726025679920, 139855209043459, 139855210919072}}, sa_flags = -1829814976, sa_restorer = 0x7c5292ee01c0}
        #5  0x00007f329493efe2 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-1.so.3
        No symbol table info available.
        #6  0x00007f329496a4c1 in _dbus_warn_check_failed () from /usr/lib/x86_64-linux-gnu/libdbus-1.so.3
        No symbol table info available.
        #7  0x000055a79cecf02a in cancel_request (conn=<optimized out>, msg=0x7c3292ef3d40, user_data=<optimized out>) at client/agent.c:258
        No locals.
        #8  0x000055a79cf63ac1 in process_message (connection=0x7c5292ee01c0, message=0x7c3292ef3d40, method=0x55a79d0445e0 <auto_methods+320>, iface_user_data=<optimized out>) at gdbus/object.c:293
                reply = <optimized out>
        #9  0x00007f329494b0f4 in dbus_connection_dispatch () from /usr/lib/x86_64-linux-gnu/libdbus-1.so.3
        No symbol table info available.
        #10 0x000055a79cf53728 in message_dispatch (data=0x7c5292ee01c0) at gdbus/mainloop.c:59
                conn = 0x7c5292ee01c0
        #11 0x00007f32949e2b9b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
        No symbol table info available.
        #12 0x00007f32949e41d7 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
        No symbol table info available.
        #13 0x00007f32949e4577 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
        No symbol table info available.
        #14 0x000055a79cf96ec9 in mainloop_run () at src/shared/mainloop-glib.c:65
        No locals.
        #15 0x000055a79cf977fb in mainloop_run_with_signal (func=func@entry=0x55a79cf8e840 <signal_callback>, user_data=user_data@entry=0x0) at src/shared/mainloop-notify.c:196
                data = 0x7b6292ee1810
                io = 0x7b7292ee1f90
                ret = <optimized out>
        #16 0x000055a79cf92a1c in bt_shell_run () at src/shared/shell.c:1476
                status = <optimized out>
                submenu = <optimized out>
        #17 0x000055a79ceb7935 in main (argc=<optimized out>, argv=<optimized out>) at client/main.c:4228
                client = 0x7c3292ee0440
                status = <optimized out>
                timeout = <optimized out>
                timeout_id = <optimized out>"


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-24 19:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 15:46 [PATCH BlueZ v3 0/9] Add HID over GATT functional tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 1/9] shared/gatt-client: Fix calling destroy after unregistering notify Luiz Augusto von Dentz
2026-09-24 19:16   ` bluez.test.bot [this message]
2026-10-09 19:52   ` Add HID over GATT functional tests bluez.test.bot
2026-09-24 15:46 ` [PATCH BlueZ v3 2/9] attrib: Fix unregistering notifications registered with bt_gatt_client Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 3/9] client/gatt: Fix setting descriptor value from scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 4/9] client/mgmt: Print Connection Subrate event Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 5/9] emulator: Default to the latest BR/EDR+LE version Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 6/9] client/scripts: Add HoG device scripts Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 7/9] doc: Add functional-hog documentation Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 8/9] test: functional: add HoG tests Luiz Augusto von Dentz
2026-09-24 15:46 ` [PATCH BlueZ v3 9/9] test: functional: limit the workers by the memory available Luiz Augusto von Dentz
2026-09-29 20:50 ` [PATCH BlueZ v3 0/9] Add HID over GATT functional tests patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2026-09-24 13:55 [PATCH BlueZ v2 1/8] attrib: Fix unregistering notifications registered with bt_gatt_client Luiz Augusto von Dentz
2026-09-24 15:25 ` Add HID over GATT functional tests bluez.test.bot
2026-09-23 19:31 [PATCH BlueZ v1 1/7] client/gatt: Fix setting descriptor value from scripts Luiz Augusto von Dentz
2026-09-23 22:30 ` Add HID over GATT functional tests 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=6ab576f0.0c0d0188.361926.08e3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.