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| pw131145 [PATCH] clarify purpose of empty cache lines
Date: Mon, 04 Sep 2023 04:32:55 -0700 (PDT)	[thread overview]
Message-ID: <64f5c067.630a0220.238a.17d3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Monday, September 04 2023 08:43:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0

131145 --> 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               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | 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

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-04 11:32 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 11:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06  2:51 dpdklab
2023-09-06  2:40 dpdklab
2023-09-06  2:34 dpdklab
2023-09-06  2:29 dpdklab
2023-09-05 15:16 dpdklab
2023-09-05 15:15 dpdklab
2023-09-05 15:11 dpdklab
2023-09-05 15:06 dpdklab
2023-09-04 12:05 dpdklab
2023-09-04 12:03 dpdklab
2023-09-04 12:02 dpdklab
2023-09-04 12:02 dpdklab
2023-09-04 11:54 dpdklab
2023-09-04 11:43 dpdklab
2023-09-04 11:31 dpdklab
2023-09-04 11:21 dpdklab
2023-09-04 11:20 dpdklab
2023-09-04 11:17 dpdklab
2023-09-04 11:15 dpdklab
2023-09-04 11:10 dpdklab
2023-09-04 11:09 dpdklab
2023-09-04 11:09 dpdklab
2023-09-04 11:07 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:06 dpdklab
2023-09-04 11:04 dpdklab
2023-09-04 11:02 dpdklab
2023-09-04 11:00 dpdklab
2023-09-04 10:58 dpdklab
2023-09-04 10:57 dpdklab
2023-09-04 10:56 dpdklab
2023-09-04 10:48 dpdklab
2023-09-04 10:35 dpdklab
2023-09-04 10:34 dpdklab
2023-09-04 10:32 dpdklab
2023-09-04 10:32 dpdklab
2023-09-04 10:31 dpdklab
2023-09-04 10:30 dpdklab
2023-09-04 10:29 dpdklab
2023-09-04 10:26 dpdklab
2023-09-04 10:24 dpdklab
2023-09-04 10:23 dpdklab
2023-09-04 10:20 dpdklab
2023-09-04 10:19 dpdklab
2023-09-04 10:19 dpdklab
2023-09-04 10:16 dpdklab
2023-09-04 10:16 dpdklab
2023-09-04 10:15 dpdklab
2023-09-04 10:14 dpdklab
     [not found] <20230904084349.12044-1-mb@smartsharesystems.com>
2023-09-04  8:41 ` qemudev
2023-09-04  8:45 ` qemudev
2023-09-04  9:59 ` 0-day Robot

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=64f5c067.630a0220.238a.17d3SMTPIN_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).