From: al-sw-devops@alabs.net
To: test-report@dpdk.org, atrwajee@amazon.com, shaibran@amazon.com
Subject: |SUCCESS| pw159007-159008 Description: SUCCESS
Date: Mon, 1 Dec 2025 11:52:59 +0200 (IST) [thread overview]
Message-ID: <513162344.1809.1764582779357@ip-10-159-234-77.eu-west-1.compute.internal> (raw)
[-- Attachment #1: Type: text/plain, Size: 5104 bytes --]
Test-Name: DPDK Fast test suite
Test-Label: aws-unit-testing
Test-Status: SUCCESS
_Unit Testing PASS_
http://dpdk.org/patch/159008
Test Status Summary:
+--------------+------------------+
| Architecture | DPDK Unit Test |
+--------------+------------------+
| x86_64 | Not Tested |
+--------------+------------------+
| arm64 | PASS |
+--------------+------------------+
Test environment (aarch64):
Description: SUCCESS
OS : Ubuntu 24.04.1 LTS
Kernel : 6.14.0-1017-aws
NIC : Elastic Network Adapter
GCC : 13.3.0-6ubuntu2~24.04
Test last 100 lines (aarch64)
Processing lib/gpudev/meson.build
Processing lib/sched/meson.build
Processing lib/acl/meson.build
Processing lib/rcu/meson.build
Processing lib/member/meson.build
Processing lib/port/meson.build
Processing lib/meter/meson.build
Processing lib/efd/meson.build
Processing lib/hash/meson.build
Processing lib/ethdev/meson.build
Processing lib/power/meson.build
Processing lib/argparse/meson.build
Processing lib/kvargs/meson.build
Processing lib/metrics/meson.build
Processing lib/cfgfile/meson.build
Processing lib/jobstats/meson.build
Processing lib/mldev/meson.build
Processing lib/fib/meson.build
Processing lib/ipsec/meson.build
Processing lib/stack/meson.build
Processing lib/ptr_compress/meson.build
Processing lib/cryptodev/meson.build
Processing lib/node/meson.build
Processing lib/security/meson.build
Processing lib/distributor/meson.build
Processing lib/latencystats/meson.build
Processing lib/graph/meson.build
Processing app/meson.build
Processing app/test-gpudev/meson.build
Processing app/test-cmdline/meson.build
Processing app/test-bbdev/meson.build
Processing app/test-mldev/meson.build
Processing app/test-regex/meson.build
Processing app/test-pmd/meson.build
Processing app/test-crypto-perf/meson.build
Processing app/test-acl/meson.build
Processing app/pdump/meson.build
Processing app/test-eventdev/meson.build
Processing app/test-security-perf/meson.build
Processing app/test-dma-perf/meson.build
Processing app/test-sad/meson.build
Processing app/test-fib/meson.build
Processing app/test-pipeline/meson.build
Processing app/test-flow-perf/meson.build
Processing app/proc-info/meson.build
Processing app/test/meson.build
Processing app/test/test_cfgfiles/meson.build
Processing app/test/bpf/meson.build
Processing app/test/suites/meson.build
Processing app/graph/meson.build
Processing app/test-compress-perf/meson.build
Processing app/dumpcap/meson.build
Running test build...
Directory already configured.
Just run your build command (e.g. ninja) and Meson will regenerate as necessary.
Run "meson setup --reconfigure" to force Meson to regenerate.
If build failures persist, run "meson setup --wipe" to rebuild from scratch
using the same options as passed when configuring the build.
ninja: Entering directory `build'
[1/36] Generating app/test/test_symlink with a custom command
[2/36] Compiling C object app/dpdk-testpmd.p/test-pmd_cmdline.c.o
[3/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_deq_cn20k_deq_112_127_tmo_seg_burst.c.o
[4/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn20k_tx_64_79_seg.c.o
[5/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn20k_tx_96_111_seg.c.o
[6/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_80_95_seg.c.o
[7/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn10k_tx_112_127_seg.c.o
[8/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn20k_tx_80_95_seg.c.o
[9/36] Compiling C object drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_tx_cn20k_tx_112_127_seg.c.o
[10/36] Linking static target drivers/libtmp_rte_event_cnxk.a
[11/36] Generating drivers/rte_event_cnxk.pmd.c with a custom command
[12/36] Compiling C object drivers/librte_event_cnxk.so.26.0.p/meson-generated_.._rte_event_cnxk.pmd.c.o
[13/36] Compiling C object drivers/librte_event_cnxk.a.p/meson-generated_.._rte_event_cnxk.pmd.c.o
[14/36] Linking static target drivers/librte_event_cnxk.a
[15/36] Generating drivers/rte_event_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[16/36] Linking target drivers/librte_event_cnxk.so.26.0
[17/36] Linking target app/dpdk-test-compress-perf
[18/36] Linking target app/dpdk-proc-info
[19/36] Linking target app/dpdk-test-mldev
[20/36] Linking target app/dpdk-test-cmdline
[21/36] Linking target app/dpdk-test-bbdev
[22/36] Linking target app/dpdk-test-pipeline
[23/36] Linking target app/dpdk-test-dma-perf
[24/36] Linking target app/dpdk-test-acl
[25/36] Linking target app/dpdk-test-regex
[26/36] Linking target app/dpdk-test-sad
[27/36] Linking target app/dpdk-test-fib
[28/36] Linking target app/dpdk-pdump
[29/36] Linking target app/dpdk-test-security-perf
[30/36] Linking target app/dpdk-test-crypto-perf
[31/36] Linking target app/dpdk-test-gpudev
[32/36] Linking target app/dpdk-graph
[33/36] Linking target app/dpdk-test-flow-perf
[34/36] Linking target app/dpdk-test-eventdev
[35/36] Linking target app/dpdk-testpmd
[36/36] Linking target app/dpdk-test
reply other threads:[~2025-12-01 9:53 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=513162344.1809.1764582779357@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).