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, Ciara Power <ciara.power@intel.com>
Subject: [dpdk-test-report] |FAILURE| pw101772-101785 [PATCH] [v4, 14/14] test/crypto: add test for chacha20_poly1305 PMD
Date: Fri, 15 Oct 2021 18:00:23 -0400 (EDT)	[thread overview]
Message-ID: <20211015220023.5FD8960524@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Ciara Power <ciara.power@intel.com>
Date: Friday, October 15 2021 14:39:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b95af1946ab4fde8489f8a91199d3b5579918997

101772-101785 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | FAIL           |
+------------------+----------------+

==== 20 line log output for Ubuntu 20.04 ARM (dpdk_unit_test): ====
85/94 DPDK:fast-tests / thash_autotest                 OK               0.32s
86/94 DPDK:fast-tests / trace_autotest                 OK               0.47s
87/94 DPDK:fast-tests / telemetry_json_autotest        OK               0.45s
88/94 DPDK:fast-tests / telemetry_data_autotest        OK               0.40s
89/94 DPDK:fast-tests / ring_pmd_autotest              OK               0.32s
90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK               1.25s
91/94 DPDK:fast-tests / bitratestats_autotest          OK               0.31s
92/94 DPDK:fast-tests / latencystats_autotest          OK               0.33s
93/94 DPDK:fast-tests / pdump_autotest                 OK               5.41s
94/94 DPDK:fast-tests / compressdev_autotest           SKIP             0.44s   exit status 77


Ok:                 88
Expected Fail:      0
Fail:               0
Unexpected Pass:    0
Skipped:            5
Timeout:            1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-15 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 22:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-15 20:24 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=20211015220023.5FD8960524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ciara.power@intel.com \
    --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).