automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>, zhoumin@loongson.cn
Subject: |WARNING| pw145985 [PATCH] test/fib: fix RCU tests
Date: Tue, 15 Oct 2024 15:32:34 +0800	[thread overview]
Message-ID: <202410150732.49F7WYZm3720712@localhost.localdomain> (raw)
In-Reply-To: <20241015075111.968663-1-david.marchand@redhat.com>

Test-Label: loongarch-compilation
Test-Status: WARNING
http://dpdk.org/patch/145985

_apply patch failure_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tue, 15 Oct 2024 09:51:11 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 19d463aacd5a5345365075db65deb8e9b3003654

Apply patch set 145985 failed:

Checking patch app/test/test_fib.c...
error: while searching for:
test_invalid_rcu(void)
{
	struct rte_fib *fib = NULL;
	struct rte_fib_conf config;
	size_t sz;
	struct rte_rcu_qsbr *qsv;
	struct rte_rcu_qsbr *qsv2;

error: patch failed: app/test/test_fib.c:389
error: app/test/test_fib.c: patch does not apply


       reply	other threads:[~2024-10-15  8:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241015075111.968663-1-david.marchand@redhat.com>
2024-10-15  7:32 ` qemudev [this message]
2024-10-15  7:52 ` |SUCCESS| " checkpatch
2024-10-15 10:51 ` dpdklab
2024-10-15 10:59 ` dpdklab
2024-10-15 11:00 ` dpdklab
2024-10-15 11:04 ` dpdklab
2024-10-15 21:23 ` dpdklab
2024-10-15 23:36 ` dpdklab
2024-10-15 23:45 ` dpdklab
2024-10-16  2:21 ` |PENDING| " dpdklab
2024-10-16  3:12 ` |SUCCESS| " dpdklab
2024-10-16  3:16 ` |PENDING| " dpdklab
2024-10-16  3:54 ` |SUCCESS| " dpdklab
2024-10-16  3:54 ` dpdklab
2024-10-16  4:06 ` |PENDING| " dpdklab
2024-10-16  4:20 ` |SUCCESS| " dpdklab
2024-10-16  6:16 ` |PENDING| " dpdklab
2024-10-16  7:06 ` |SUCCESS| " dpdklab
2024-10-16  9:24 ` dpdklab
2024-10-16  9:25 ` dpdklab
2024-10-16 18:02 ` |WARNING| " dpdklab
2024-10-22 14:09 ` |SUCCESS| " dpdklab

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=202410150732.49F7WYZm3720712@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=zhoumin@loongson.cn \
    /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).