All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org,
	devnull+emil.l.velikov.gmail.com@kernel.org
Subject: RE: Handful of build fixes and cleanups
Date: Wed, 14 Feb 2024 15:18:28 -0800 (PST)	[thread overview]
Message-ID: <65cd4a44.630a0220.d3b66.0b96@mx.google.com> (raw)
In-Reply-To: <20240214-hook-fixup-v1-1-0e158ffea140@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.12 seconds
GitLint                       PASS      0.89 seconds
BuildEll                      PASS      23.94 seconds
BluezMake                     PASS      724.63 seconds
MakeCheck                     PASS      11.86 seconds
MakeDistcheck                 PASS      164.98 seconds
CheckValgrind                 PASS      228.99 seconds
CheckSmatch                   PASS      331.74 seconds
bluezmakeextell               PASS      108.25 seconds
IncrementalBuild              FAIL      1354.33 seconds
ScanBuild                     PASS      971.65 seconds

Details
##############################
Test: IncrementalBuild - FAIL
Desc: Incremental build with the patches in the series
Output:

error: tools/97-hid2hci.rules: already exists in working directory
hint: Use 'git am --show-current-patch' to see the failed patch


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2024-02-14 23:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 22:01 [PATCH BlueZ 0/4] Handful of build fixes and cleanups Emil Velikov
2024-02-14 22:01 ` Emil Velikov via B4 Relay
2024-02-14 22:01 ` [PATCH BlueZ 1/4] build: fold separate install-data-hooks Emil Velikov
2024-02-14 22:01   ` Emil Velikov via B4 Relay
2024-02-14 22:23   ` Luiz Augusto von Dentz
2024-02-14 23:22     ` Emil Velikov
2024-02-14 23:18   ` bluez.test.bot [this message]
2024-02-14 22:01 ` [PATCH BlueZ 2/4] build: install obexd (dbus,systemd} services as needed Emil Velikov
2024-02-14 22:01   ` Emil Velikov via B4 Relay
2024-02-14 22:01 ` [PATCH BlueZ 3/4] build: drop %.rules make rule Emil Velikov
2024-02-14 22:01   ` Emil Velikov via B4 Relay
2024-02-14 22:01 ` [PATCH BlueZ 4/4] build: simplify coverage handling Emil Velikov
2024-02-14 22:01   ` Emil Velikov via B4 Relay
  -- strict thread matches above, loose matches on Subject: below --
2024-02-16 23:11 [PATCH BlueZ v2 01/10] build: rework {install-data,uninstall}-hook Emil Velikov
2024-02-17  0:31 ` Handful of build fixes and cleanups bluez.test.bot

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=65cd4a44.630a0220.d3b66.0b96@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=devnull+emil.l.velikov.gmail.com@kernel.org \
    --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.