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, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 6dad0bb5c8621644beca86ff5f4910a943ba604d
Date: Tue, 29 Oct 2024 12:47:27 -0700 (PDT)	[thread overview]
Message-ID: <67213bcf.050a0220.17f214.79c1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

6dad0bb5c8621644beca86ff5f4910a943ba604d --> testing pass

Upstream job id: Generic-DPDK-Compile-Meson#326083

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: Depends on container host
	Compiler: gcc 9.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31309/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-10-29 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 19:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-29 22:34 dpdklab
2024-10-29 20:56 dpdklab
2024-10-28 18:41 dpdklab
2024-10-28 18:34 dpdklab
2024-10-28 18:31 dpdklab
2024-10-28 18:27 dpdklab
2024-10-28 18:27 dpdklab
2024-10-28 18:26 dpdklab
2024-10-28 18:20 dpdklab
2024-10-28 18:19 dpdklab
2024-10-28 18:14 dpdklab
2024-10-28 18:14 dpdklab
2024-10-28 18:10 dpdklab
2024-10-28 18:06 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=67213bcf.050a0220.17f214.79c1SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jerinj@marvell.com \
    --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).