All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ] test: functional: retry pairable when Busy
Date: Sat, 10 Oct 2026 16:52:08 -0700 (PDT)	[thread overview]
Message-ID: <6acacfa8.33ea1a9e.2790f.b821@mx.google.com> (raw)
In-Reply-To: <32b040dbaa0b8bffa4746203c5232791574604ee.1791671481.git.pav@iki.fi>

[-- Attachment #1: Type: text/plain, Size: 2541 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/1183123/

---Test result---

Test Summary:
CheckPatch                    PASS      0.43 seconds
GitLint                       FAIL      0.33 seconds
BuildEll                      PASS      19.45 seconds
BluezMake                     PASS      395.99 seconds
MakeCheck                     PASS      14.27 seconds
MakeDistcheck                 PASS      140.10 seconds
CheckValgrind                 PASS      231.14 seconds
CheckSmatch                   PASS      291.30 seconds
bluezmakeextell               PASS      94.29 seconds
TestFunctional                FAIL      1192.23 seconds
IncrementalBuild              PASS      388.67 seconds
ScanBuild                     PASS      1125.24 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] test: functional: retry pairable when Busy

22: B3 Line contains hard tab characters (\t): "[bluetoothctl]> 	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb"
23: B3 Line contains hard tab characters (\t): "[bluetoothctl]> 	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb"
##############################
Test: TestFunctional - FAIL
Desc: Run test-functional
Output:
FAIL functional.test_bearer::test_bearer_le_connect[hosts14-vm2]: pytest_bluezenv.rpc.RemoteError: Got event.kind='org.bluez.Agent1.RequestAuthorization', expected kinds=('org.bluez.Adapter1.StartDiscovery:reply',)
    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/agent.py", line 108, in expect
            raise AssertionError(f"Got {event.kind=}, expected {kinds=}")
        AssertionError: Got event.kind='org.bluez.Agent1.RequestAuthorization', expected kinds=('org.bluez.Adapter1.StartDiscovery:reply',)


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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-10-10 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 22:32 [PATCH BlueZ] test: functional: retry pairable when Busy Pauli Virtanen
2026-10-10 23:52 ` 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=6acacfa8.33ea1a9e.2790f.b821@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 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.