public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Hall <bearodark@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [v5] Bluetooth: btusb: Add MediaTek MT7925-B22M support ID 0x13d3:0x3604
Date: Tue, 30 Jul 2024 19:50:09 -0700	[thread overview]
Message-ID: <1e91f3da-9e31-4f14-949b-25e718cb6541@gmail.com> (raw)
In-Reply-To: <66a96a28.050a0220.81785.560d@mx.google.com>

I'm confused on why TestRunner_mgmt-tester is now failing, it seems to 
be a test on the

patch itself (and on v3 of this patch it did not fail, which has an 
identical codechange).

I do not wish to resend an identical patch and waste CI time if there is 
indeed something wrong with the patch,

but I would like to be advised if this is a spurious/unrelated failure, 
and if so should I resend the patch? or is there a mechanism to rerun 
these tests

On 7/30/24 3:33 PM, bluez.test.bot@gmail.com wrote:
> 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=875239
>
> ---Test result---
>
> Test Summary:
> CheckPatch                    PASS      0.60 seconds
> GitLint                       PASS      0.28 seconds
> SubjectPrefix                 PASS      0.10 seconds
> BuildKernel                   PASS      30.26 seconds
> CheckAllWarning               PASS      32.87 seconds
> CheckSparse                   PASS      38.26 seconds
> CheckSmatch                   PASS      103.58 seconds
> BuildKernel32                 PASS      29.18 seconds
> TestRunnerSetup               PASS      532.97 seconds
> TestRunner_l2cap-tester       PASS      24.24 seconds
> TestRunner_iso-tester         PASS      37.44 seconds
> TestRunner_bnep-tester        PASS      5.00 seconds
> TestRunner_mgmt-tester        FAIL      110.67 seconds
> TestRunner_rfcomm-tester      PASS      7.70 seconds
> TestRunner_sco-tester         PASS      15.18 seconds
> TestRunner_ioctl-tester       PASS      8.14 seconds
> TestRunner_mesh-tester        PASS      6.16 seconds
> TestRunner_smp-tester         PASS      7.12 seconds
> TestRunner_userchan-tester    PASS      5.19 seconds
> IncrementalBuild              PASS      28.22 seconds
>
> Details
> ##############################
> Test: TestRunner_mgmt-tester - FAIL
> Desc: Run mgmt-tester with test-runner
> Output:
> Total: 492, Passed: 489 (99.4%), Failed: 1, Not Run: 2
>
> Failed Test Cases
> LL Privacy - Start Discovery 2 (Disable RL)          Failed       0.175 seconds
>
>
> ---
> Regards,
> Linux Bluetooth
>

  reply	other threads:[~2024-07-31  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 22:08 [PATCH v5] Bluetooth: btusb: Add MediaTek MT7925-B22M support ID 0x13d3:0x3604 Alexander Hall
2024-07-30 22:33 ` [v5] " bluez.test.bot
2024-07-31  2:50   ` Alex Hall [this message]
2024-08-06 20:28 ` [PATCH v5] " patchwork-bot+bluetooth

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=1e91f3da-9e31-4f14-949b-25e718cb6541@gmail.com \
    --to=bearodark@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox