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, Renyong Wan <wanry@3snic.com>
Subject: |FAILURE| pw130789-130812 [PATCH] [32/32] net/sssnic: add VF dev sup
Date: Tue, 29 Aug 2023 04:48:56 -0700 (PDT)	[thread overview]
Message-ID: <64eddb28.050a0220.991ea.eae8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130812

_Testing issues_

Submitter: Renyong Wan <wanry@3snic.com>
Date: Tuesday, August 29 2023 07:58:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ac1d4db91e9955148e82f2caaa107434409cf35e

130789-130812 --> testing fail

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)           | FAIL               |
+------------------------------------+--------------------+
| Fedora 37 (ARM)                    | FAIL               |
+------------------------------------+--------------------+
| CentOS Stream 9 (ARM)              | FAIL               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | FAIL               |
+------------------------------------+--------------------+

==== 20 line log output for Ubuntu 20.04 ARM GCC Cross Compile (dpdk_meson_compile): ====

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-29 11:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 11:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-29 12:12 dpdklab
2023-08-29 12:03 dpdklab
2023-08-29 12:02 dpdklab
2023-08-29 12:01 dpdklab
2023-08-29 12:01 dpdklab
2023-08-29 11:59 dpdklab
2023-08-29 11:58 dpdklab
2023-08-29 11:57 dpdklab
2023-08-29 11:57 dpdklab
2023-08-29 11:55 dpdklab
2023-08-29 11:54 dpdklab
2023-08-29 11:52 dpdklab
2023-08-29 11:52 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:50 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:48 dpdklab
2023-08-29 11:47 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:44 dpdklab
2023-08-29 11:42 dpdklab
2023-08-29 11:41 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=64eddb28.050a0220.991ea.eae8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=wanry@3snic.com \
    /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).