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: test-runner: use virtio-fs by default, functional test speedup
Date: Thu, 10 Sep 2026 12:30:27 -0700 (PDT)	[thread overview]
Message-ID: <6aa30553.c355708a.30d4d2.9abf@mx.google.com> (raw)
In-Reply-To: <05bba57a2d407b44212415591ffd7f4dcce4098b.1789058875.git.pav@iki.fi>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.09 seconds
GitLint                       FAIL      0.64 seconds
BuildEll                      PASS      19.55 seconds
BluezMake                     PASS      378.20 seconds
MakeCheck                     PASS      14.21 seconds
MakeDistcheck                 PASS      139.98 seconds
CheckValgrind                 PASS      231.49 seconds
CheckSmatch                   PASS      291.19 seconds
bluezmakeextell               PASS      93.97 seconds
IncrementalBuild              PASS      375.56 seconds
ScanBuild                     PASS      1118.25 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,2/2] tools: test-runner: use virtiofsd for filesystem passthrough
WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#188: FILE: tools/test-runner.c:525:
+		const char *cmd[] = {

/github/workspace/src/patch/14805955.patch total: 0 errors, 1 warnings, 334 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/patch/14805955.patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,2/2] tools: test-runner: use virtiofsd for filesystem passthrough

14: B3 Line contains hard tab characters (\t): "real	2m9,736s"
15: B3 Line contains hard tab characters (\t): "user	1m29,570s"
16: B3 Line contains hard tab characters (\t): "sys	0m32,715s"
20: B3 Line contains hard tab characters (\t): "real	1m35,703s"
21: B3 Line contains hard tab characters (\t): "user	0m28,938s"
22: B3 Line contains hard tab characters (\t): "sys	0m7,453s"


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-10 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 16:48 [PATCH BlueZ 0/2] test-runner: use virtio-fs by default, functional test speedup Pauli Virtanen
2026-09-10 16:48 ` [PATCH BlueZ 1/2] doc: enable virtio-fs in tester kernel configs Pauli Virtanen
2026-09-10 19:30   ` bluez.test.bot [this message]
2026-09-10 16:48 ` [PATCH BlueZ 2/2] tools: test-runner: use virtiofsd for filesystem passthrough Pauli Virtanen
2026-09-10 17:16   ` Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2026-09-12 18:18 [PATCH BlueZ v2 1/4] tools/test-runner: replace alloca() based argv setup Pauli Virtanen
2026-09-12 19:17 ` test-runner: use virtio-fs by default, functional test speedup 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=6aa30553.c355708a.30d4d2.9abf@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.