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, Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw105237 [PATCH] eal: fix data race in multi-process support
Date: Fri, 17 Dec 2021 18:59:05 +0000 (UTC)	[thread overview]
Message-ID: <20211217185905.AB5C76025C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/105237

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, December 17 2021 18:16:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:042f5a355a57b31a9f87824173a9d427b21abdb8

105237 --> testing fail

Test environment and result as below:

+-------------------------------+--------------+----------------+
|          Environment          | lpm_autotest | dpdk_unit_test |
+===============================+==============+================+
| Ubuntu 20.04 ARM SVE          | FAIL         | SKIPPED        |
+-------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM GCC Native   | SKIPPED      | FAIL           |
+-------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM Clang Native | SKIPPED      | FAIL           |
+-------------------------------+--------------+----------------+

==== 20 line log output for Ubuntu 20.04 ARM Clang Native (dpdk_unit_test): ====
89/99 DPDK:fast-tests / trace_autotest        FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
90/99 DPDK:fast-tests / metrics_autotest      FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
91/99 DPDK:fast-tests / telemetry_json_autotest  FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
92/99 DPDK:fast-tests / telemetry_data_autotest  FAIL     0.12 s (exit status 255 or signal 127 SIGinvalid)
93/99 DPDK:fast-tests / ring_pmd_autotest     FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
94/99 DPDK:fast-tests / event_eth_tx_adapter_autotest  FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
95/99 DPDK:fast-tests / bitratestats_autotest  FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
96/99 DPDK:fast-tests / latencystats_autotest  FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
97/99 DPDK:fast-tests / pdump_autotest        FAIL     0.07 s (exit status 255 or signal 127 SIGinvalid)
98/99 DPDK:fast-tests / vdev_autotest         FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)
99/99 DPDK:fast-tests / compressdev_autotest  FAIL     0.04 s (exit status 255 or signal 127 SIGinvalid)

Ok:                    0
Expected Fail:         0
Fail:                 99
Unexpected Pass:       0
Skipped:               0
Timeout:               0

Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-VM-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====

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 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-12-17 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 18:59 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-17 18:48 dpdklab
2021-12-17 18:48 dpdklab
2021-12-17 18:42 dpdklab
2021-12-17 18:40 dpdklab
2021-12-17 18:39 dpdklab
     [not found] <20211217181649.154972-1-stephen@networkplumber.org>
2021-12-17 18:39 ` 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=20211217185905.AB5C76025C@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).