automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143593 [PATCH] [v1,1/1] usertools: add DPDK build direct
Date: Wed, 04 Sep 2024 18:08:03 -0700 (PDT)	[thread overview]
Message-ID: <66d90473.620a0220.6f564.dd23SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <d961787cf29192bf329fec0cc0ac25e6397743f6.1725462616.git.anatoly.burakov@intel.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143593

_Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wednesday, September 04 2024 15:17:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143593 --> testing pass

Upstream job id: Template-DTS-Pipeline#178381

Test environment and result as below:

+--------------------+----------------------+
|    Environment     | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS                 |
+--------------------+----------------------+
| Ubuntu 22.04       | PASS                 |
+--------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-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/30903/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-09-05  1:08 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d961787cf29192bf329fec0cc0ac25e6397743f6.1725462616.git.anatoly.burakov@intel.com>
2024-09-04 14:55 ` |SUCCESS| pw143593 [PATCH v1 1/1] usertools: add DPDK build directory setup script qemudev
2024-09-04 15:00 ` qemudev
2024-09-04 15:18 ` |WARNING| " checkpatch
2024-09-04 16:04 ` |SUCCESS| " 0-day Robot
2024-09-04 21:56 ` |SUCCESS| pw143593 [PATCH] [v1,1/1] usertools: add DPDK build direct dpdklab
2024-09-04 22:03 ` dpdklab
2024-09-04 23:49 ` dpdklab
2024-09-04 23:50 ` dpdklab
2024-09-05  0:27 ` dpdklab
2024-09-05  0:33 ` dpdklab
2024-09-05  0:45 ` dpdklab
2024-09-05  0:45 ` |PENDING| " dpdklab
2024-09-05  0:49 ` dpdklab
2024-09-05  0:57 ` |SUCCESS| " dpdklab
2024-09-05  0:57 ` |PENDING| " dpdklab
2024-09-05  1:01 ` |SUCCESS| " dpdklab
2024-09-05  1:08 ` dpdklab [this message]
2024-09-05  1:10 ` dpdklab
2024-09-05  2:19 ` dpdklab
2024-09-05  2:20 ` dpdklab
2024-09-05  2:21 ` dpdklab
2024-09-05  2:27 ` dpdklab
2024-09-05  2:36 ` dpdklab
2024-09-05  2:45 ` dpdklab
2024-09-05  2:47 ` dpdklab
2024-09-05  2:55 ` dpdklab
2024-09-05  2:57 ` dpdklab
2024-09-05  2:59 ` dpdklab
2024-09-05  3:01 ` dpdklab
2024-09-05  3:02 ` dpdklab
2024-09-05  3:02 ` dpdklab
2024-09-05  3:03 ` dpdklab
2024-09-05  3:04 ` dpdklab
2024-09-05  3:04 ` dpdklab
2024-09-05  3:22 ` dpdklab
2024-09-05  3:30 ` dpdklab
2024-09-05  3:30 ` dpdklab
2024-09-05  3:33 ` dpdklab
2024-09-05  3:34 ` dpdklab
2024-09-05  3:34 ` dpdklab
2024-09-05  3:36 ` dpdklab
2024-09-05  3:37 ` dpdklab
2024-09-05  3:37 ` dpdklab
2024-09-05  3:43 ` dpdklab
2024-09-05  3:43 ` dpdklab
2024-09-05  3:44 ` dpdklab
2024-09-05  3:45 ` dpdklab
2024-09-05  3:45 ` dpdklab
2024-09-05  3:48 ` dpdklab
2024-09-05  3:51 ` dpdklab
2024-09-05  4:22 ` dpdklab
2024-09-05  8:34 ` dpdklab
2024-09-05  9:14 ` dpdklab
2024-09-05 17:24 ` dpdklab
2024-09-05 19:45 ` dpdklab
2024-09-18  6:21 ` dpdklab
2024-09-18  6:40 ` dpdklab
2024-09-18  6:51 ` dpdklab
2024-09-18  7:11 ` 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=66d90473.620a0220.6f564.dd23SMTPIN_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).