From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw145764 [PATCH] [RFC,v2] net: 2-byte align packed headers
Date: Wed, 30 Oct 2024 09:08:28 -0700 (PDT) [thread overview]
Message-ID: <672259fc.050a0220.26ca87.4677SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011160653.88028-1-mb@smartsharesystems.com>
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/145764
_apply patch failure_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, October 11 2024 16:06:53
Applied on: CommitID:2a682d65f8dbe1e8be9cc2425095827e18c700e3
Apply patch set 145764 failed:
<!doctype html>
<html lang="en">
<head>
<title>Not Found</title>
</head>
<body>
<h1>Not Found</h1><p>The requested resource was not found on this server.</p>
</body>
</html>
https://lab.dpdk.org/results/dashboard/patchsets/31438/
UNH-IOL DPDK Community Lab
prev parent reply other threads:[~2024-10-30 16:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011160653.88028-1-mb@smartsharesystems.com>
2024-10-11 15:39 ` |SUCCESS| pw145764 [RFC PATCH v2] " qemudev
2024-10-11 15:43 ` qemudev
2024-10-11 16:08 ` |WARNING| " checkpatch
2024-10-11 17:02 ` |SUCCESS| " 0-day Robot
2024-10-13 17:25 ` |SUCCESS| pw145764 [PATCH] [RFC,v2] " dpdklab
2024-10-13 17:28 ` dpdklab
2024-10-13 17:29 ` dpdklab
2024-10-13 17:30 ` dpdklab
2024-10-13 17:35 ` dpdklab
2024-10-13 17:40 ` dpdklab
2024-10-13 18:02 ` dpdklab
2024-10-13 18:14 ` dpdklab
2024-10-13 18:35 ` dpdklab
2024-10-13 23:34 ` dpdklab
2024-10-13 23:35 ` dpdklab
2024-10-13 23:53 ` |PENDING| " dpdklab
2024-10-14 0:35 ` |SUCCESS| " dpdklab
2024-10-14 1:27 ` |FAILURE| " dpdklab
2024-10-14 2:14 ` |SUCCESS| " dpdklab
2024-10-14 3:06 ` |PENDING| " dpdklab
2024-10-14 7:44 ` |SUCCESS| " dpdklab
2024-10-14 10:19 ` dpdklab
2024-10-21 18:28 ` dpdklab
2024-10-21 18:32 ` dpdklab
2024-10-22 4:42 ` dpdklab
2024-10-22 9:46 ` dpdklab
2024-10-30 16:08 ` dpdklab [this message]
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=672259fc.050a0220.26ca87.4677SMTPIN_ADDED_MISSING@mx.google.com \
--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).