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, Tal Shnaiderman <talshn@nvidia.com>
Subject: [dpdk-test-report] |FAILURE| pw102752-102756 [PATCH] [v3, 5/5] crypto/mlx5: support on Windows
Date: Mon, 25 Oct 2021 16:32:42 -0400 (EDT)	[thread overview]
Message-ID: <20211025203242.EC97C60524@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/102756

_Testing issues_

Submitter: Tal Shnaiderman <talshn@nvidia.com>
Date: Monday, October 25 2021 08:46:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:daa02b5cddbb8e11b31d41e2bf7bb1ae64dcae2f

102752-102756 --> 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): ====
88/97 DPDK:fast-tests / thash_autotest                 OK               0.30s
89/97 DPDK:fast-tests / trace_autotest                 OK               0.40s
90/97 DPDK:fast-tests / telemetry_json_autotest        OK               0.38s
91/97 DPDK:fast-tests / telemetry_data_autotest        OK               0.44s
92/97 DPDK:fast-tests / ring_pmd_autotest              OK               0.26s
93/97 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK               1.28s
94/97 DPDK:fast-tests / bitratestats_autotest          OK               0.27s
95/97 DPDK:fast-tests / latencystats_autotest          OK               0.29s
96/97 DPDK:fast-tests / pdump_autotest                 OK               5.44s
97/97 DPDK:fast-tests / compressdev_autotest           SKIP             0.38s   exit status 77


Ok:                 92
Expected Fail:      0
Fail:               0
Unexpected Pass:    0
Skipped:            4
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/19686/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-25 20:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 20:32 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-25 22:44 dpdklab
2021-10-25 19:54 dpdklab
2021-10-25 18:51 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=20211025203242.EC97C60524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=talshn@nvidia.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).