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| pw117862 [PATCH] [v1, 34/35] net/ionic: retry init commands up to five times
Date: Mon, 10 Oct 2022 22:19:01 -0400 (EDT)	[thread overview]
Message-ID: <20221011021901.E48D56D509@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_apply patch failure_

Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Tuesday, October 11 2022 00:50:31 
Applied on: CommitID:f13604fad12a81383da7b04821a4befb3d01e2ed
Apply patch set 117862 failed:

Checking patch drivers/net/ionic/ionic_dev.h...
error: while searching for:

#define IONIC_DEVCMD_TIMEOUT		5	/* devcmd_timeout */
#define IONIC_DEVCMD_CHECK_PERIOD_US	10	/* devcmd status chk period */

#define IONIC_ALIGN			4096


error: patch failed: drivers/net/ionic/ionic_dev.h:24
Checking patch drivers/net/ionic/ionic_lif.c...
Hunk #1 succeeded at 1339 (offset -84 lines).
Hunk #2 succeeded at 1616 (offset -104 lines).
Checking patch drivers/net/ionic/ionic_main.c...
Applying patch drivers/net/ionic/ionic_dev.h with 1 reject...
Rejected hunk #1.
Applied patch drivers/net/ionic/ionic_lif.c cleanly.
Applied patch drivers/net/ionic/ionic_main.c cleanly.
diff a/drivers/net/ionic/ionic_dev.h b/drivers/net/ionic/ionic_dev.h	(rejected hunks)
@@ -24,6 +24,7 @@
 
 #define IONIC_DEVCMD_TIMEOUT		5	/* devcmd_timeout */
 #define IONIC_DEVCMD_CHECK_PERIOD_US	10	/* devcmd status chk period */
+#define IONIC_DEVCMD_RETRY_WAIT_US	20000
 
 #define IONIC_ALIGN			4096
 

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2022-10-11  2:19 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=20221011021901.E48D56D509@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).