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| pw130766-130765 [PATCH] [2/2] devtools: forbid use of buil
Date: Fri, 25 Aug 2023 09:13:56 -0700 (PDT)	[thread overview]
Message-ID: <64e8d344.810a0220.3e988.af37SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, August 25 2023 10:18:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c

130766-130765 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | 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)

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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/27444/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-25 16:13 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 16:13 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-25 20:58 dpdklab
2023-08-25 20:46 dpdklab
2023-08-25 19:41 dpdklab
2023-08-25 19:29 dpdklab
2023-08-25 18:40 dpdklab
2023-08-25 18:22 dpdklab
2023-08-25 17:52 dpdklab
2023-08-25 17:50 dpdklab
2023-08-25 17:50 dpdklab
2023-08-25 17:39 dpdklab
2023-08-25 17:22 dpdklab
2023-08-25 17:03 dpdklab
2023-08-25 16:36 dpdklab
2023-08-25 16:32 dpdklab
2023-08-25 16:18 dpdklab
2023-08-25 16:18 dpdklab
2023-08-25 16:18 dpdklab
2023-08-25 16:16 dpdklab
2023-08-25 16:15 dpdklab
2023-08-25 16:15 dpdklab
2023-08-25 16:14 dpdklab
2023-08-25 16:11 dpdklab
2023-08-25 16:10 dpdklab
2023-08-25 16:08 dpdklab
2023-08-25 16:07 dpdklab
2023-08-25 16:07 dpdklab
2023-08-25 16:06 dpdklab
2023-08-25 16:05 dpdklab
2023-08-25 16:05 dpdklab
2023-08-25 16:04 dpdklab
2023-08-25 16:03 dpdklab
2023-08-25 16:03 dpdklab
2023-08-25 16:02 dpdklab
2023-08-25 16:02 dpdklab
2023-08-25 16:00 dpdklab
2023-08-25 16:00 dpdklab
2023-08-25 15:59 dpdklab
2023-08-25 15:58 dpdklab
2023-08-25 15:58 dpdklab
2023-08-25 15:57 dpdklab
2023-08-25 15:57 dpdklab
2023-08-25 15:57 dpdklab
2023-08-25 15:57 dpdklab
2023-08-25 15:41 dpdklab
2023-08-25 15:40 dpdklab
2023-08-25 15:40 dpdklab
2023-08-25 15:36 dpdklab
2023-08-25 15:34 dpdklab
2023-08-25 15:33 dpdklab
2023-08-25 15:31 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=64e8d344.810a0220.3e988.af37SMTPIN_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).