RE: test-runner: use virtio-fs by default, functional test speedup

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/1163573/

---Test result---

Test Summary:
CheckPatch                    FAIL      2.15 seconds
GitLint                       FAIL      1.33 seconds
BuildEll                      PASS      19.81 seconds
BluezMake                     PASS      373.66 seconds
MakeCheck                     PASS      14.08 seconds
MakeDistcheck                 PASS      141.19 seconds
CheckValgrind                 PASS      237.21 seconds
CheckSmatch                   PASS      298.62 seconds
bluezmakeextell               PASS      97.14 seconds
IncrementalBuild              PASS      417.21 seconds
ScanBuild                     PASS      1131.54 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,1/4] tools/test-runner: replace alloca() based argv setup
WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __printf(2, 3) over __attribute__((format(printf, 2, 3)))
#129: FILE: tools/test-runner.c:81:
+static void __attribute__((format(printf, 2, 3)))

/github/workspace/src/patch/14810752.patch total: 0 errors, 1 warnings, 202 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/14810752.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.


[BlueZ,v2,3/4] tools/test-runner: use virtiofsd for filesystem passthrough
WARNING:VOLATILE: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst
#199: FILE: tools/test-runner.c:571:
+static volatile sig_atomic_t terminate;

WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#284: FILE: tools/test-runner.c:656:
+		const char *cmd[] = {

/github/workspace/src/patch/14810754.patch total: 0 errors, 2 warnings, 371 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/14810754.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,v2,3/4] 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/2522

---
Regards,
Linux Bluetooth