From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, soenke.huster@eknoes.de
Subject: RE: [v2] Bluetooth: RFCOMM: Use skb_trim to trim checksum
Date: Fri, 10 Jun 2022 04:57:46 -0700 (PDT) [thread overview]
Message-ID: <62a331ba.1c69fb81.67749.24cf@mx.google.com> (raw)
In-Reply-To: <20220610110749.110881-1-soenke.huster@eknoes.de>
[-- Attachment #1: Type: text/plain, Size: 1458 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=649266
---Test result---
Test Summary:
CheckPatch PASS 0.78 seconds
GitLint PASS 0.42 seconds
SubjectPrefix PASS 0.31 seconds
BuildKernel PASS 31.50 seconds
BuildKernel32 PASS 30.28 seconds
Incremental Build with patchesPASS 39.69 seconds
TestRunner: Setup PASS 487.85 seconds
TestRunner: l2cap-tester PASS 18.02 seconds
TestRunner: bnep-tester PASS 5.79 seconds
TestRunner: mgmt-tester FAIL 106.97 seconds
TestRunner: rfcomm-tester PASS 9.38 seconds
TestRunner: sco-tester PASS 9.27 seconds
TestRunner: smp-tester PASS 9.11 seconds
TestRunner: userchan-tester PASS 6.15 seconds
Details
##############################
Test: TestRunner: mgmt-tester - FAIL - 106.97 seconds
Run test-runner with mgmt-tester
Total: 493, Passed: 491 (99.6%), Failed: 2, Not Run: 0
Failed Test Cases
Add Advertising - Success (Name+data+appear) Timed out 2.769 seconds
Add Ext Advertising - Success (Name+data+appear) Timed out 2.405 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-06-10 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:07 [PATCH v2] Bluetooth: RFCOMM: Use skb_trim to trim checksum Soenke Huster
2022-06-10 11:57 ` bluez.test.bot [this message]
2022-06-10 13:59 ` Eric Dumazet
2022-06-10 15:35 ` Sönke Huster
2022-06-10 16:55 ` Eric Dumazet
2022-06-14 13:42 ` Sönke Huster
2022-06-14 14:17 ` Eric Dumazet
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=62a331ba.1c69fb81.67749.24cf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=soenke.huster@eknoes.de \
/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.