From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Functional/integration testing
Date: Fri, 20 Mar 2026 15:14:59 -0700 (PDT) [thread overview]
Message-ID: <69bdc6e3.050a0220.272073.e056@mx.google.com> (raw)
In-Reply-To: <c2a503373330ebcfa8f8a20f8378cfda5d17634c.1774041047.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1991 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=1070106
---Test result---
Test Summary:
CheckPatch PENDING 0.50 seconds
GitLint PENDING 0.40 seconds
BuildEll PASS 20.67 seconds
BluezMake PASS 637.64 seconds
MakeCheck PASS 18.96 seconds
MakeDistcheck FAIL 79.18 seconds
CheckValgrind PASS 291.31 seconds
CheckSmatch WARNING 351.20 seconds
bluezmakeextell PASS 180.73 seconds
IncrementalBuild PENDING 0.44 seconds
ScanBuild PASS 988.84 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
/usr/bin/ld: tools/test-runner.o: in function `start_controller_forward':
/github/workspace/src/src/bluez-5.86/_build/sub/../../tools/test-runner.c:989: undefined reference to `openpty'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:6062: tools/test-runner] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:4148: all] Error 2
make: *** [Makefile:10668: distcheck] Error 1
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/btdev.c:480:29: warning: Variable length array is used.
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
https://github.com/bluez/bluez/pull/1979/checks
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-20 22:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 21:10 [PATCH BlueZ v2 00/20] Functional/integration testing Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 01/20] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-03-20 22:14 ` bluez.test.bot [this message]
2026-03-20 21:10 ` [PATCH BlueZ v2 02/20] emulator: btvirt: allow specifying where server unix sockets are made Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 03/20] emulator: btvirt: support SCO data packets Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 04/20] emulator: btdev: clear more state on Reset Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 05/20] test-runner: enable path argument for --unix Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 06/20] test-runner: Add -o/--option option Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 07/20] test-runner: allow source tree root for -k Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 08/20] doc: enable CONFIG_VIRTIO_CONSOLE in tester config Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 09/20] test-runner: use virtio-serial for implementing -u device forwarding Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 10/20] doc: enable KVM paravirtualization & clock support in tester kernel config Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 11/20] doc: add functional/integration testing documentation Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 12/20] test: add functional/integration testing framework Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 13/20] test: functional: add Pipewire-using audio streaming tests Pauli Virtanen
2026-03-20 21:10 ` [PATCH BlueZ v2 14/20] test: functional: add --btmon option to start btmon Pauli Virtanen
2026-03-20 21:12 ` Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 15/20] build: add functional testing target Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 16/20] test: functional: impose Python code formatting Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 17/20] test: functional: add option for building kernel image first Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 18/20] test: functional: add custom Agent1 implementation for testing Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 19/20] test: functional: warn on kernel warning/bug messages Pauli Virtanen
2026-03-20 21:12 ` [PATCH BlueZ v2 20/20] test: functional: add basic obex file transfer tests Pauli Virtanen
-- strict thread matches above, loose matches on Subject: below --
2026-03-22 21:29 [PATCH BlueZ v3 01/20] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-03-22 22:38 ` Functional/integration testing bluez.test.bot
2026-02-28 12:51 [PATCH BlueZ 01/11] emulator: btvirt: check pkt lengths, don't get stuck on malformed Pauli Virtanen
2026-02-28 13:45 ` Functional/integration testing 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=69bdc6e3.050a0220.272073.e056@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox