From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Joakim.Tjernlund@infinera.com
Subject: RE: bluez SEGV in current master
Date: Wed, 14 Jun 2023 06:52:40 -0700 (PDT) [thread overview]
Message-ID: <6489c628.0c0a0220.34218.0c96@mx.google.com> (raw)
In-Reply-To: <6704ebbea9d1bb64e54b45b1b3d6cd321b28971b.camel@infinera.com>
[-- Attachment #1: Type: text/plain, Size: 4293 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=757099
---Test result---
Test Summary:
CheckPatch FAIL 1.02 seconds
GitLint FAIL 0.74 seconds
BuildEll PASS 27.26 seconds
BluezMake PASS 861.75 seconds
MakeCheck PASS 12.27 seconds
MakeDistcheck PASS 153.25 seconds
CheckValgrind PASS 250.95 seconds
CheckSmatch PASS 338.03 seconds
bluezmakeextell PASS 101.49 seconds
IncrementalBuild PASS 702.53 seconds
ScanBuild PASS 1039.34 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
bluez SEGV in current master
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#128:
Jun 13 13:38:15 systemd-coredump[3941]: Process 1897 (bluetoothd) of user 0 dumped core.
/github/workspace/src/src/13279998.patch total: 0 errors, 1 warnings, 18 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/13279998.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 SEGV in current master
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
7: B1 Line exceeds max length (88>80): "Jun 13 13:38:15 systemd-coredump[3941]: Process 1897 (bluetoothd) of user 0 dumped core."
9: B1 Line exceeds max length (106>80): " #0 0x0000556bea93277a a2dp_resume_complete (bluetoothd + 0x3e77a)"
10: B1 Line exceeds max length (101>80): " #1 0x0000556bea9210a2 finalize_resume (bluetoothd + 0x2d0a2)"
11: B1 Line exceeds max length (102>80): " #2 0x0000556bea92afaf avdtp_start_resp (bluetoothd + 0x36faf)"
12: B1 Line exceeds max length (98>80): " #6 0x0000556bea9dcc85 mainloop_run (bluetoothd + 0xe8c85)"
13: B1 Line exceeds max length (110>80): " #7 0x0000556bea9dd0dc mainloop_run_with_signal (bluetoothd + 0xe90dc)"
14: B1 Line exceeds max length (90>80): " #8 0x0000556bea91a4ef main (bluetoothd + 0x264ef)"
15: B1 Line exceeds max length (92>80): " #11 0x0000556bea91ace1 _start (bluetoothd + 0x26ce1)"
16: B1 Line exceeds max length (95>80): "Jun 13 13:38:15 systemd[1]: bluetooth.service: Main process exited, code=dumped, status=11/SEGV"
21: B3 Line contains hard tab characters (\t): "342 static void a2dp_resume_complete(struct avdtp *session, int err,"
22: B3 Line contains hard tab characters (\t): "343 void *user_data)"
23: B3 Line contains hard tab characters (\t): "344 {"
24: B3 Line contains hard tab characters (\t): "345 struct media_owner *owner = user_data;"
25: B3 Line contains hard tab characters (\t): "346 struct media_request *req = owner->pending;"
26: B3 Line contains hard tab characters (\t): "347 struct media_transport *transport = owner->transport;"
27: B3 Line contains hard tab characters (\t): "348 struct a2dp_sep *sep = media_endpoint_get_sep(transport->endpoint);"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-06-14 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 12:29 bluez SEGV in current master Joakim Tjernlund
2023-06-14 13:52 ` bluez.test.bot [this message]
2023-06-14 16:25 ` Luiz Augusto von Dentz
2023-06-14 16:32 ` Joakim Tjernlund
2023-06-14 16:53 ` Luiz Augusto von Dentz
2023-06-14 17:00 ` Joakim Tjernlund
2023-06-27 8:35 ` Joakim Tjernlund
2023-06-27 13:14 ` Joakim Tjernlund
2023-06-29 16:58 ` Joakim Tjernlund
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=6489c628.0c0a0220.34218.0c96@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Joakim.Tjernlund@infinera.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.