automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: David Christensen <drc@linux.vnet.ibm.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129024 [PATCH] config/ppc: fix gcc "internal compiler er
Date: Tue, 27 Jun 2023 15:13:18 -0700 (PDT)	[thread overview]
Message-ID: <649b5efe.050a0220.e6e37.9530SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-aarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129024

_Testing PASS_

Submitter: David Christensen <drc@linux.vnet.ibm.com>
Date: Tuesday, June 27 2023 20:54:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f504f9722a22b90af708ce2e5dd6d360289bef90

129024 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+---------------------------+--------------+------------------------------+
|         Environment         | dpdk_unit_test | cryptodev_sw_zuc_autotest | lpm_autotest | cryptodev_sw_snow3g_autotest |
+=============================+================+===========================+==============+==============================+
| (32-bit) ARM Ubuntu 20.04.4 | PASS           | SKIPPED                   | SKIPPED      | SKIPPED                      |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+
| Debian 11                   | SKIPPED        | PASS                      | SKIPPED      | PASS                         |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | SKIPPED                   | PASS         | SKIPPED                      |
+-----------------------------+----------------+---------------------------+--------------+------------------------------+


(32-bit) ARM Ubuntu 20.04.4
	Kernel: 5.4.0-148-generic aarch64
	Compiler: gcc 9.4

Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-27 22:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 22:13 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-28  3:41 dpdklab
2023-06-28  2:43 dpdklab
2023-06-28  2:35 dpdklab
2023-06-27 23:11 dpdklab
2023-06-27 22:42 dpdklab
2023-06-27 22:10 dpdklab
2023-06-27 22:09 dpdklab
2023-06-27 22:08 dpdklab
2023-06-27 22:06 dpdklab
2023-06-27 21:54 dpdklab
2023-06-27 21:48 dpdklab
2023-06-27 21:48 dpdklab
2023-06-27 21:48 dpdklab
2023-06-27 21:47 dpdklab
2023-06-27 21:47 dpdklab
2023-06-27 21:43 dpdklab
2023-06-27 21:40 dpdklab
2023-06-27 21:40 dpdklab
2023-06-27 21:39 dpdklab
2023-06-27 21:37 dpdklab
2023-06-27 21:36 dpdklab
2023-06-27 21:33 dpdklab
2023-06-27 21:31 dpdklab
2023-06-27 21:30 dpdklab
2023-06-27 21:27 dpdklab
2023-06-27 21:26 dpdklab
2023-06-27 21:21 dpdklab
2023-06-27 21:20 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=649b5efe.050a0220.e6e37.9530SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=drc@linux.vnet.ibm.com \
    --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).