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: |PENDING| [GIT MASTER] 680818068d31764357075cde440232ce5ab8b786
Date: Sat, 14 Sep 2024 00:31:12 -0700 (PDT)	[thread overview]
Message-ID: <66e53bc0.170a0220.2ad5ae.1efcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v21.11

680818068d31764357075cde440232ce5ab8b786 --> testing pending

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

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM)                        | PEND               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+


RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: Depends on container host
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-09-14  7:31 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14  7:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-19 15:02 dpdklab
2024-09-19 12:23 dpdklab
2024-09-19 11:46 dpdklab
2024-09-19 11:36 dpdklab
2024-09-19 10:12 dpdklab
2024-09-18  6:27 dpdklab
2024-09-18  6:21 dpdklab
2024-09-17  7:06 dpdklab
2024-09-17  6:33 dpdklab
2024-09-16  5:02 dpdklab
2024-09-16  5:01 dpdklab
2024-09-16  4:53 dpdklab
2024-09-15  5:30 dpdklab
2024-09-15  5:02 dpdklab
2024-09-15  4:48 dpdklab
2024-09-15  4:44 dpdklab
2024-09-15  4:38 dpdklab
2024-09-14  5:43 dpdklab
2024-09-14  5:35 dpdklab
2024-09-14  5:24 dpdklab
2024-09-13  8:49 dpdklab
2024-09-13  6:50 dpdklab
2024-09-13  6:30 dpdklab
2024-09-13  5:36 dpdklab
2024-09-13  5:23 dpdklab
2024-09-12 12:35 dpdklab
2024-09-12 11:57 dpdklab
2024-09-12 11:45 dpdklab
2024-09-11 13:47 dpdklab
2024-09-11  8:32 dpdklab
2024-09-11  8:00 dpdklab
2024-09-11  7:13 dpdklab
2024-09-11  7:04 dpdklab
2024-09-10 11:23 dpdklab
2024-09-10 10:11 dpdklab
2024-09-10  9:23 dpdklab
2024-09-10  5:27 dpdklab
2024-09-09  7:04 dpdklab
2024-09-09  5:53 dpdklab
2024-09-09  5:17 dpdklab
2024-09-09  5:10 dpdklab
2024-09-09  4:51 dpdklab
2024-09-08  5:23 dpdklab
2024-09-08  5:08 dpdklab
2024-09-08  4:37 dpdklab
2024-09-07 15:01 dpdklab
2024-09-07 10:15 dpdklab
2024-09-07  9:37 dpdklab
2024-09-07  7:43 dpdklab
2024-09-07  4:47 dpdklab
2024-09-06 22:11 dpdklab
2024-09-06 11:20 dpdklab
2024-09-06 11:04 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=66e53bc0.170a0220.2ad5ae.1efcSMTPIN_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).