From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145917-145918 [PATCH] [v3,2/2] ethdev: fix potential rac
Date: Mon, 14 Oct 2024 18:10:43 -0700 (PDT) [thread overview]
Message-ID: <670dc113.170a0220.dcf13.07caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241014193237.1992382-3-rjarry@redhat.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145918
_Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Monday, October 14 2024 19:32:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5f7b98189de733080656989d63b0e7ffd249830a
145917-145918 --> testing pass
Upstream job id: Template-DTS-Pipeline#188071
Test environment and result as below:
+--------------------+----------------------+
| Environment | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS |
+--------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31477/
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-10-15 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241014193237.1992382-3-rjarry@redhat.com>
2024-10-14 19:25 ` |SUCCESS| pw145917-145918 [PATCH dpdk v3 2/2] ethdev: fix potential race in telemetry endpoints qemudev
2024-10-14 19:29 ` |FAILURE| " qemudev
2024-10-14 19:33 ` |SUCCESS| pw145918 " checkpatch
2024-10-14 20:22 ` |FAILURE| " 0-day Robot
2024-10-15 1:10 ` dpdklab [this message]
2024-10-15 3:16 ` |SUCCESS| pw145917-145918 [PATCH] [v3,2/2] ethdev: fix potential rac dpdklab
2024-10-15 4: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=670dc113.170a0220.dcf13.07caSMTPIN_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).