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| pw132359 [PATCH] doc/guides: refer to generic binding devi
Date: Fri, 06 Oct 2023 16:02:08 -0700 (PDT)	[thread overview]
Message-ID: <652091f0.810a0220.dff16.5c5eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132359

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, October 06 2023 12:55:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3bcd5b3198d4a31176b1ac73fc7236a12186fffe

132359 --> testing pass

Test environment and result as below:

+--------------------------------------+--------------------+
|             Environment              | dpdk_meson_compile |
+======================================+====================+
| Ubuntu 20.04 ARM SVE                 | PASS               |
+--------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)             | PASS               |
+--------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS               |
+--------------------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27843/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-06 23:02 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06 23:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-07  0:16 dpdklab
2023-10-07  0:11 dpdklab
2023-10-07  0:10 dpdklab
2023-10-07  0:04 dpdklab
2023-10-06 23:51 dpdklab
2023-10-06 23:48 dpdklab
2023-10-06 23:47 dpdklab
2023-10-06 23:36 dpdklab
2023-10-06 23:33 dpdklab
2023-10-06 23:32 dpdklab
2023-10-06 23:29 dpdklab
2023-10-06 23:28 dpdklab
2023-10-06 23:25 dpdklab
2023-10-06 23:22 dpdklab
2023-10-06 23:21 dpdklab
2023-10-06 23:17 dpdklab
2023-10-06 23:14 dpdklab
2023-10-06 23:10 dpdklab
2023-10-06 23:06 dpdklab
2023-10-06 23:05 dpdklab
2023-10-06 23:03 dpdklab
2023-10-06 23:01 dpdklab
2023-10-06 22:58 dpdklab
2023-10-06 22:58 dpdklab
2023-10-06 22:55 dpdklab
2023-10-06 22:55 dpdklab
2023-10-06 22:51 dpdklab
2023-10-06 22:50 dpdklab
2023-10-06 22:50 dpdklab
2023-10-06 22:46 dpdklab
2023-10-06 22:43 dpdklab
2023-10-06 22:41 dpdklab
2023-10-06 22:39 dpdklab
2023-10-06 22:35 dpdklab
2023-10-06 22:34 dpdklab
2023-10-06 22:33 dpdklab
2023-10-06 22:33 dpdklab
2023-10-06 22:33 dpdklab
2023-10-06 22:32 dpdklab
2023-10-06 22:32 dpdklab
2023-10-06 22:31 dpdklab
2023-10-06 22:30 dpdklab
2023-10-06 22:30 dpdklab
2023-10-06 22:30 dpdklab
2023-10-06 22:28 dpdklab
2023-10-06 22:25 dpdklab
2023-10-06 22:10 dpdklab
2023-10-06 22:08 dpdklab
2023-10-06 22:07 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=652091f0.810a0220.dff16.5c5eSMTPIN_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).