From: al-sw-devops@alabs.net
To: test-report@dpdk.org, atrwajee@amazon.com, shaibran@amazon.com
Subject: |FAILURE| pw153538-155383 rework EAL argument parsing in DPDK
Date: Mon, 21 Jul 2025 21:38:29 +0300 (IDT) [thread overview]
Message-ID: <683573655.6848.1753123109758@ip-10-159-234-77.eu-west-1.compute.internal> (raw)
[-- Attachment #1: Type: text/plain, Size: 3557 bytes --]
Test-Name: DPDK Fast test suite
Test-Label: aws-unit-testing
Test-Status: FAILURE
_Unit Testing Apply error encountered_
http://dpdk.org/patch/155383
Test Status Summary:
+--------------+------------------+
| Architecture | DPDK Unit Test |
+--------------+------------------+
| x86_64 | FAILURE |
+--------------+------------------+
| arm64 | FAILURE |
+--------------+------------------+
Test environment (aarch64):
Description: Apply error encountered
OS : Ubuntu 24.04.1 LTS
Kernel : 6.8.0-1030-aws
NIC : Elastic Network Adapter
GCC : 13.3.0-6ubuntu2~24.04
Test last 100 lines (aarch64)
Cleaning repository state...
Trying to checkout branch: origin/main
Checked out to main (3795e96fc862e2b65aa8951f6661420510c87328)
Done: main commit 3795e96fc862e2b65aa8951f6661420510c87328
Trying to checkout branch: origin/main
Checked out to main (3795e96fc862e2b65aa8951f6661420510c87328)
Applying patch...
Failed to apply patch:
Applying: eal: add long options for each short option
Applying: argparse: add support for string and boolean args
Using index info to reconstruct a base tree...
M lib/argparse/rte_argparse.c
M lib/argparse/rte_argparse.h
Falling back to patching base and 3-way merge...
Auto-merging lib/argparse/rte_argparse.h
CONFLICT (content): Merge conflict in lib/argparse/rte_argparse.h
Auto-merging lib/argparse/rte_argparse.c
CONFLICT (content): Merge conflict in lib/argparse/rte_argparse.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 argparse: add support for string and boolean args
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Patch failed. Checking for conflicts in .rst files...
Patch apply failed with conflicts in non-.rst files: ['lib/argparse/rte_argparse.c', 'lib/argparse/rte_argparse.h']
FAILURE
Test environment (x86_64):
Description: Apply error encountered
OS : Ubuntu 24.04.1 LTS
Kernel : 6.8.0-1030-aws
NIC : Elastic Network Adapter
GCC : 13.3.0-6ubuntu2~24.04
Test last 100 lines (x86_64)
Cleaning repository state...
Trying to checkout branch: origin/main
Checked out to main (3795e96fc862e2b65aa8951f6661420510c87328)
Done: main commit 3795e96fc862e2b65aa8951f6661420510c87328
Trying to checkout branch: origin/main
Checked out to main (3795e96fc862e2b65aa8951f6661420510c87328)
Applying patch...
Applying: eal: add long options for each short option
Applying: argparse: add support for string and boolean args
Using index info to reconstruct a base tree...
M lib/argparse/rte_argparse.c
M lib/argparse/rte_argparse.h
Falling back to patching base and 3-way merge...
Auto-merging lib/argparse/rte_argparse.h
CONFLICT (content): Merge conflict in lib/argparse/rte_argparse.h
Auto-merging lib/argparse/rte_argparse.c
CONFLICT (content): Merge conflict in lib/argparse/rte_argparse.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 argparse: add support for string and boolean args
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Patch failed. Checking for conflicts in .rst files...
Patch apply failed with conflicts in non-.rst files: ['lib/argparse/rte_argparse.c', 'lib/argparse/rte_argparse.h']
FAILURE
reply other threads:[~2025-07-21 18:38 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=683573655.6848.1753123109758@ip-10-159-234-77.eu-west-1.compute.internal \
--to=al-sw-devops@alabs.net \
--cc=atrwajee@amazon.com \
--cc=shaibran@amazon.com \
--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).