From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129813 [PATCH] ci: fix race on container image name
Date: Wed, 02 Aug 2023 03:10:07 -0700 (PDT) [thread overview]
Message-ID: <64ca2b7f.4a0a0220.3671b.c967SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129813
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, August 02 2023 06:54:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0ae35eceb9e4569b0814fcf671b4455301bb7518
129813 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27209/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-02 10:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 10:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 14:35 dpdklab
2023-08-02 14:30 dpdklab
2023-08-02 13:38 dpdklab
2023-08-02 13:18 dpdklab
2023-08-02 13:07 dpdklab
2023-08-02 12:49 dpdklab
[not found] <20230802065404.3807143-1-david.marchand@redhat.com>
2023-08-02 6:54 ` checkpatch
2023-08-02 7:33 ` qemudev
2023-08-02 7:37 ` qemudev
2023-08-02 12:18 ` 0-day Robot
2023-08-02 11:50 dpdklab
2023-08-02 10:47 dpdklab
2023-08-02 10:20 dpdklab
2023-08-02 10:10 dpdklab
2023-08-02 9:47 dpdklab
2023-08-02 9:33 dpdklab
2023-08-02 9:32 dpdklab
2023-08-02 9:18 dpdklab
2023-08-02 9:10 dpdklab
2023-08-02 9:08 dpdklab
2023-08-02 9:04 dpdklab
2023-08-02 9:04 dpdklab
2023-08-02 9:00 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=64ca2b7f.4a0a0220.3671b.c967SMTPIN_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).