From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139727-139731 [PATCH] [RFC,v4,6/6] eal: add unit tests f
Date: Tue, 30 Apr 2024 04:00:34 -0700 (PDT) [thread overview]
Message-ID: <6630cf52.0c0a0220.b6662.9596SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240430095523.108688-7-mattias.ronnblom@ericsson.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139731
_Functional Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Tuesday, April 30 2024 09:55:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139727-139731 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29877/
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-04-30 11:00 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240430095523.108688-7-mattias.ronnblom@ericsson.com>
2024-04-30 9:43 ` |SUCCESS| pw139727-139731 [RFC v4 6/6] eal: add unit tests for atomic bit access functions qemudev
2024-04-30 9:47 ` qemudev
2024-04-30 10:45 ` |SUCCESS| pw139727-139731 [PATCH] [RFC,v4,6/6] eal: add unit tests f dpdklab
2024-04-30 10:45 ` dpdklab
2024-04-30 10:46 ` dpdklab
2024-04-30 10:46 ` dpdklab
2024-04-30 10:46 ` dpdklab
2024-04-30 10:47 ` dpdklab
2024-04-30 10:47 ` dpdklab
2024-04-30 10:47 ` dpdklab
2024-04-30 10:48 ` dpdklab
2024-04-30 10:48 ` dpdklab
2024-04-30 10:48 ` dpdklab
2024-04-30 10:48 ` dpdklab
2024-04-30 10:48 ` dpdklab
2024-04-30 10:51 ` dpdklab
2024-04-30 10:54 ` dpdklab
2024-04-30 10:55 ` dpdklab
2024-04-30 10:56 ` dpdklab
2024-04-30 10:56 ` dpdklab
2024-04-30 10:57 ` dpdklab
2024-04-30 10:57 ` dpdklab
2024-04-30 10:57 ` dpdklab
2024-04-30 10:57 ` dpdklab
2024-04-30 11:00 ` dpdklab [this message]
2024-04-30 11:00 ` dpdklab
2024-04-30 11:00 ` dpdklab
2024-04-30 11:02 ` dpdklab
2024-04-30 11:03 ` dpdklab
2024-04-30 11:03 ` |FAILURE| pw139731 [RFC v4 6/6] eal: add unit tests for atomic bit access functions 0-day Robot
2024-04-30 11:04 ` |SUCCESS| pw139727-139731 [PATCH] [RFC,v4,6/6] eal: add unit tests f dpdklab
2024-04-30 11:04 ` dpdklab
2024-04-30 11:10 ` dpdklab
2024-04-30 11:10 ` dpdklab
2024-04-30 11:10 ` dpdklab
2024-04-30 11:11 ` dpdklab
2024-04-30 11:11 ` dpdklab
2024-04-30 11:11 ` dpdklab
2024-04-30 11:12 ` dpdklab
2024-04-30 11:14 ` dpdklab
2024-04-30 11:15 ` dpdklab
2024-04-30 11:16 ` dpdklab
2024-04-30 11:19 ` dpdklab
2024-04-30 11:19 ` dpdklab
2024-04-30 11:21 ` dpdklab
2024-04-30 11:22 ` dpdklab
2024-04-30 11:22 ` dpdklab
2024-04-30 11:23 ` dpdklab
2024-04-30 11:23 ` dpdklab
2024-04-30 11:24 ` dpdklab
2024-04-30 11:24 ` dpdklab
2024-04-30 11:26 ` dpdklab
2024-04-30 11:29 ` dpdklab
2024-04-30 11:30 ` dpdklab
2024-04-30 11:31 ` dpdklab
2024-04-30 11:32 ` dpdklab
2024-04-30 11:32 ` dpdklab
2024-04-30 11:33 ` dpdklab
2024-04-30 11:34 ` |FAILURE| " dpdklab
2024-04-30 11:35 ` |SUCCESS| " dpdklab
2024-04-30 11:35 ` |FAILURE| " dpdklab
2024-04-30 11:39 ` |SUCCESS| " dpdklab
2024-04-30 11:41 ` dpdklab
2024-04-30 11:41 ` dpdklab
2024-04-30 11:44 ` |FAILURE| " dpdklab
2024-04-30 11:44 ` |SUCCESS| " dpdklab
2024-04-30 11:46 ` dpdklab
2024-04-30 11:46 ` |FAILURE| " dpdklab
2024-04-30 11:47 ` dpdklab
2024-04-30 11:48 ` dpdklab
2024-04-30 11:49 ` |SUCCESS| " dpdklab
2024-04-30 11:50 ` |FAILURE| " dpdklab
2024-04-30 11:52 ` |SUCCESS| " dpdklab
2024-04-30 11:56 ` dpdklab
2024-04-30 12:06 ` dpdklab
2024-04-30 12:07 ` dpdklab
2024-04-30 12:17 ` dpdklab
2024-04-30 12:18 ` dpdklab
2024-04-30 12:22 ` dpdklab
2024-04-30 12:42 ` dpdklab
2024-04-30 12:42 ` dpdklab
2024-04-30 12:42 ` dpdklab
2024-04-30 12:43 ` dpdklab
2024-04-30 13:15 ` dpdklab
2024-04-30 13:35 ` dpdklab
2024-04-30 13:36 ` dpdklab
2024-04-30 13:47 ` dpdklab
2024-04-30 14:10 ` dpdklab
2024-04-30 14:34 ` 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=6630cf52.0c0a0220.b6662.9596SMTPIN_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).