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| pw144053-144056 [PATCH] [v2,2/2] test/pcapng: test chained
Date: Fri, 13 Sep 2024 13:20:59 -0700 (PDT)	[thread overview]
Message-ID: <66e49eab.050a0220.40f4d.10c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <nefxl4axip5gfq4c7ployqxtnorgubcbrkugfziftcasq7jreb@bqyveydkttlq>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/144056

_Testing pending_

Submitter: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
Date: Friday, September 13 2024 13:06:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144053-144056 --> testing pending

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

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/patchsets/31026/

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-13 20:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <nefxl4axip5gfq4c7ployqxtnorgubcbrkugfziftcasq7jreb@bqyveydkttlq>
2024-09-13 12:39 ` |SUCCESS| pw144053-144056 [PATCH v2 2/2] test/pcapng: test chained mbufs qemudev
2024-09-13 12:43 ` qemudev
2024-09-13 13:07 ` |SUCCESS| pw144056 " checkpatch
2024-09-13 14:04 ` 0-day Robot
2024-09-13 19:18 ` |PENDING| pw144053-144056 [PATCH] [v2,2/2] test/pcapng: test chained dpdklab
2024-09-13 19:21 ` |SUCCESS| " dpdklab
2024-09-13 19:27 ` dpdklab
2024-09-13 19:29 ` dpdklab
2024-09-13 19:29 ` dpdklab
2024-09-13 19:37 ` dpdklab
2024-09-13 19:38 ` |PENDING| " dpdklab
2024-09-13 19:41 ` |SUCCESS| " dpdklab
2024-09-13 19:55 ` |PENDING| " dpdklab
2024-09-13 20:00 ` |SUCCESS| " dpdklab
2024-09-13 20:05 ` dpdklab
2024-09-13 20:09 ` dpdklab
2024-09-13 20:15 ` dpdklab
2024-09-13 20:20 ` dpdklab [this message]
2024-09-13 20:21 ` dpdklab
2024-09-13 20:24 ` dpdklab
2024-09-13 20:25 ` dpdklab
2024-09-13 20:36 ` dpdklab
2024-09-13 21:02 ` dpdklab
2024-09-13 21:36 ` dpdklab
2024-09-13 22:05 ` dpdklab
2024-09-15  0:06 ` dpdklab
2024-09-15  3:00 ` dpdklab
2024-09-18  4:03 ` 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=66e49eab.050a0220.40f4d.10c5SMTPIN_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).