automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw110687-110686 [PATCH] [v2, 2/2] ci: build some job with ASan
Date: Thu,  5 May 2022 12:08:36 -0400 (EDT)	[thread overview]
Message-ID: <20220505160836.06AE244239@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/110687

_apply patch failure_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, May 05 2022 09:29:52 
Applied on: CommitID:90bf3f89ed33f78e9f41818caf123e13e508dee7
Apply patch set 110687-110686 failed:

Checking patch app/test/test_memory.c...
Checking patch lib/eal/common/malloc_elem.h...
error: while searching for:

#else /* !RTE_MALLOC_ASAN */

#define __rte_no_asan

static inline void
asan_set_zone(void *ptr __rte_unused, size_t len __rte_unused,
		uint32_t val __rte_unused) { }

error: patch failed: lib/eal/common/malloc_elem.h:276
Checking patch lib/eal/include/rte_common.h...
Applied patch app/test/test_memory.c cleanly.
Applying patch lib/eal/common/malloc_elem.h with 1 reject...
Hunk #1 applied cleanly.
Hunk #2 applied cleanly.
Rejected hunk #3.
Applied patch lib/eal/include/rte_common.h cleanly.
diff a/lib/eal/common/malloc_elem.h b/lib/eal/common/malloc_elem.h	(rejected hunks)
@@ -276,8 +272,6 @@ old_malloc_size(struct malloc_elem *elem)
 
 #else /* !RTE_MALLOC_ASAN */
 
-#define __rte_no_asan
-
 static inline void
 asan_set_zone(void *ptr __rte_unused, size_t len __rte_unused,
 		uint32_t val __rte_unused) { }

https://lab.dpdk.org/results/dashboard/patchsets/22007/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-05-05 16:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220505160836.06AE244239@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).