automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw95646 [PATCH] [v2] dmadev: introduce DMA device library
Date: Sun, 11 Jul 2021 06:11:30 -0400 (EDT)	[thread overview]
Message-ID: <20210711101130.7CF53B0F7@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/95646

_Testing issues_

Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Sunday, July 11 2021 09:25:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a95bbb72623c310df4d0c8ad45c2ee06f538e01b

95646 --> testing fail

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Ubuntu 18.04 ARM | PASS     |
+------------------+----------+
| FreeBSD 13       | FAIL     |
+------------------+----------+
| Ubuntu 18.04     | PASS     |
+------------------+----------+
| Ubuntu 20.04     | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| Fedora 32        | PASS     |
+------------------+----------+

==== 20 line log output for FreeBSD 13 (abi_test): ====

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (10 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Error: cannot find librte_event_octeontx.dump in build_install
Functions changes summary: 0 Removed, 0 Changed, 0 Added (6 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (54 filtered out), 0 Added (11 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

==== End log output ====

Ubuntu 18.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-07-11 10:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-11 10:11 dpdklab [this message]
     [not found] <1625995556-41473-1-git-send-email-fengchengwen@huawei.com>
2021-07-11  9:31 ` [dpdk-test-report] |WARNING| pw95646 [PATCH v2] " checkpatch

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=20210711101130.7CF53B0F7@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@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).