All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, eatabakhsh04@gmail.com
Subject: RE: obexd: launch obexd directly from dbus service
Date: Tue, 28 Feb 2023 22:13:10 -0800 (PST)	[thread overview]
Message-ID: <63feecf6.e90a0220.f7abe.ba24@mx.google.com> (raw)
In-Reply-To: <20230301050242.47225-1-eatabakhsh04@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2872 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=725708

---Test result---

Test Summary:
CheckPatch                    FAIL      0.72 seconds
GitLint                       FAIL      0.52 seconds
BuildEll                      PASS      27.14 seconds
BluezMake                     PASS      859.79 seconds
MakeCheck                     PASS      11.92 seconds
MakeDistcheck                 PASS      150.99 seconds
CheckValgrind                 PASS      244.70 seconds
CheckSmatch                   PASS      331.61 seconds
bluezmakeextell               PASS      98.85 seconds
IncrementalBuild              PASS      715.91 seconds
ScanBuild                     PASS      1021.10 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
obexd: launch obexd directly from dbus service
WARNING:TYPO_SPELLING: 'Whenver' may be misspelled - perhaps 'Whenever'?
#80: 
Whenver obexd is summoned via dbus with the systemdservice file, the
^^^^^^^

WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#81: 
daemon exits with the following error: Failed to start org.bluez.obex service: Process org.bluez.obex exite.

WARNING:TYPO_SPELLING: 'whenver' may be misspelled - perhaps 'whenever'?
#83: 
whenver an app calls for obexd via dbus, it seems like it forces to use
^^^^^^^

/github/workspace/src/src/13155603.patch total: 0 errors, 3 warnings, 5 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/src/13155603.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:
obexd: launch obexd directly from dbus service

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
4: B1 Line exceeds max length (108>80): "daemon exits with the following error: Failed to start org.bluez.obex service: Process org.bluez.obex exite."


---
Regards,
Linux Bluetooth


      reply	other threads:[~2023-03-01  6:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  5:02 [PATCH] obexd: launch obexd directly from dbus service Erfaun Atabakhsh
2023-03-01  6:13 ` 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=63feecf6.e90a0220.f7abe.ba24@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=eatabakhsh04@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.