From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143071-143072 [PATCH] [v3,5/5] eal: extend bitops to han
Date: Mon, 12 Aug 2024 06:55:10 -0700 (PDT) [thread overview]
Message-ID: <66ba143e.050a0220.157790.6f5aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240812124930.604796-6-mattias.ronnblom@ericsson.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143072
_Functional Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Monday, August 12 2024 12:49:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143071-143072 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#174552
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| coremask | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30766/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-08-12 13:55 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240812124930.604796-6-mattias.ronnblom@ericsson.com>
2024-08-12 12:33 ` |SUCCESS| pw143071-143072 [PATCH v3 5/5] eal: extend bitops to handle volatile pointers qemudev
2024-08-12 12:38 ` qemudev
2024-08-12 13:00 ` |WARNING| pw143072 " checkpatch
2024-08-12 13:24 ` |SUCCESS| pw143071-143072 [PATCH] [v3,5/5] eal: extend bitops to han dpdklab
2024-08-12 13:33 ` dpdklab
2024-08-12 13:36 ` dpdklab
2024-08-12 13:36 ` |PENDING| " dpdklab
2024-08-12 13:37 ` dpdklab
2024-08-12 13:37 ` dpdklab
2024-08-12 13:38 ` |SUCCESS| " dpdklab
2024-08-12 13:43 ` |PENDING| " dpdklab
2024-08-12 13:44 ` dpdklab
2024-08-12 13:46 ` dpdklab
2024-08-12 13:46 ` dpdklab
2024-08-12 13:49 ` dpdklab
2024-08-12 13:49 ` |SUCCESS| " dpdklab
2024-08-12 13:49 ` |PENDING| " dpdklab
2024-08-12 13:50 ` dpdklab
2024-08-12 13:51 ` |SUCCESS| " dpdklab
2024-08-12 13:52 ` |PENDING| " dpdklab
2024-08-12 13:54 ` dpdklab
2024-08-12 13:54 ` dpdklab
2024-08-12 13:55 ` |SUCCESS| " dpdklab
2024-08-12 13:55 ` dpdklab [this message]
2024-08-12 13:57 ` |PENDING| " dpdklab
2024-08-12 14:00 ` dpdklab
2024-08-12 14:01 ` dpdklab
2024-08-12 14:02 ` dpdklab
2024-08-12 14:02 ` |FAILURE| pw143072 [PATCH v3 5/5] eal: extend bitops to handle volatile pointers 0-day Robot
2024-08-12 14:02 ` |PENDING| pw143071-143072 [PATCH] [v3,5/5] eal: extend bitops to han dpdklab
2024-08-12 14:04 ` dpdklab
2024-08-12 14:04 ` |SUCCESS| " dpdklab
2024-08-12 14:07 ` dpdklab
2024-08-12 14:08 ` |PENDING| " dpdklab
2024-08-12 14:08 ` dpdklab
2024-08-12 14:09 ` dpdklab
2024-08-12 14:09 ` dpdklab
2024-08-12 14:09 ` dpdklab
2024-08-12 14:11 ` dpdklab
2024-08-12 14:11 ` |FAILURE| " dpdklab
2024-08-12 14:12 ` dpdklab
2024-08-12 14:12 ` |PENDING| " dpdklab
2024-08-12 14:13 ` dpdklab
2024-08-12 14:13 ` |SUCCESS| " dpdklab
2024-08-12 14:14 ` |PENDING| " dpdklab
2024-08-12 14:14 ` |FAILURE| " dpdklab
2024-08-12 14:15 ` |PENDING| " dpdklab
2024-08-12 14:15 ` |SUCCESS| " dpdklab
2024-08-12 14:16 ` dpdklab
2024-08-12 14:16 ` |FAILURE| " dpdklab
2024-08-12 14:16 ` |PENDING| " dpdklab
2024-08-12 14:17 ` dpdklab
2024-08-12 14:17 ` dpdklab
2024-08-12 14:17 ` |SUCCESS| " dpdklab
2024-08-12 14:18 ` |FAILURE| " dpdklab
2024-08-12 14:20 ` |PENDING| " dpdklab
2024-08-12 14:22 ` |FAILURE| " dpdklab
2024-08-12 14:24 ` |PENDING| " dpdklab
2024-08-12 14:26 ` |FAILURE| " dpdklab
2024-08-12 14:27 ` |PENDING| " dpdklab
2024-08-12 14:27 ` |FAILURE| " dpdklab
2024-08-12 14:28 ` |SUCCESS| " dpdklab
2024-08-12 14:31 ` |PENDING| " dpdklab
2024-08-12 14:32 ` |FAILURE| " dpdklab
2024-08-12 14:35 ` dpdklab
2024-08-12 14:36 ` |PENDING| " dpdklab
2024-08-12 14:36 ` |SUCCESS| " dpdklab
2024-08-12 14:37 ` |PENDING| " dpdklab
2024-08-12 14:39 ` |FAILURE| " dpdklab
2024-08-12 14:40 ` dpdklab
2024-08-12 14:40 ` |SUCCESS| " dpdklab
2024-08-12 14:42 ` |PENDING| " dpdklab
2024-08-12 14:43 ` |FAILURE| " dpdklab
2024-08-12 14:44 ` |PENDING| " dpdklab
2024-08-12 14:48 ` |FAILURE| " dpdklab
2024-08-12 14:49 ` |PENDING| " dpdklab
2024-08-12 14:50 ` |FAILURE| " dpdklab
2024-08-12 14:50 ` |SUCCESS| " dpdklab
2024-08-12 14:52 ` |PENDING| " dpdklab
2024-08-12 14:52 ` dpdklab
2024-08-12 14:52 ` |FAILURE| " dpdklab
2024-08-12 14:58 ` |PENDING| " dpdklab
2024-08-12 15:00 ` dpdklab
2024-08-12 15:06 ` dpdklab
2024-08-12 15:08 ` dpdklab
2024-08-12 15:08 ` dpdklab
2024-08-12 15:08 ` dpdklab
2024-08-12 15:26 ` dpdklab
2024-08-12 15:28 ` dpdklab
2024-08-12 15:33 ` dpdklab
2024-08-12 15:34 ` dpdklab
2024-08-12 15:36 ` dpdklab
2024-08-12 15:41 ` dpdklab
2024-08-12 15:43 ` dpdklab
2024-08-12 15:44 ` |SUCCESS| " dpdklab
2024-08-12 15:44 ` |PENDING| " dpdklab
2024-08-12 15:59 ` dpdklab
2024-08-12 16:08 ` dpdklab
2024-08-12 16:22 ` dpdklab
2024-08-12 16:52 ` |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=66ba143e.050a0220.157790.6f5aSMTPIN_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).