From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in m
Date: Tue, 19 Mar 2024 00:30:22 -0700 (PDT) [thread overview]
Message-ID: <65f93f0e.6b0a0220.354e1.1e22SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319141454.3275543-1-jingjing.wu@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138477
_Testing PASS_
Submitter: Jingjing Wu <jingjing.wu@intel.com>
Date: Tuesday, March 19 2024 14:14:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138477 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29590/
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-03-19 7:30 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319141454.3275543-1-jingjing.wu@intel.com>
2024-03-19 5:59 ` |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in mcore dispatch qemudev
2024-03-19 6:05 ` |FAILURE| " qemudev
2024-03-19 6:23 ` |SUCCESS| " checkpatch
2024-03-19 7:10 ` |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in m dpdklab
2024-03-19 7:10 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:17 ` dpdklab
2024-03-19 7:18 ` dpdklab
2024-03-19 7:19 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:20 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:23 ` |FAILURE| " dpdklab
2024-03-19 7:23 ` |SUCCESS| " dpdklab
2024-03-19 7:23 ` |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in mcore dispatch 0-day Robot
2024-03-19 7:24 ` |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in m dpdklab
2024-03-19 7:26 ` dpdklab
2024-03-19 7:27 ` dpdklab
2024-03-19 7:29 ` dpdklab
2024-03-19 7:30 ` dpdklab [this message]
2024-03-19 7:30 ` |SUCCESS| " dpdklab
2024-03-19 7:32 ` |FAILURE| " dpdklab
2024-03-19 7:32 ` dpdklab
2024-03-19 7:33 ` dpdklab
2024-03-19 7:34 ` |SUCCESS| " dpdklab
2024-03-19 7:41 ` |FAILURE| " dpdklab
2024-03-19 7:41 ` dpdklab
2024-03-19 7:42 ` dpdklab
2024-03-19 7:46 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:56 ` dpdklab
2024-03-19 7:57 ` dpdklab
2024-03-19 8:03 ` dpdklab
2024-03-19 8:25 ` |SUCCESS| " dpdklab
2024-03-21 4:18 ` dpdklab
2024-03-21 5:18 ` 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=65f93f0e.6b0a0220.354e1.1e22SMTPIN_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).