From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] 4f914d656b427c621c3757c23fca7ed9de8ffe79
Date: Tue, 24 Aug 2021 14:34:19 -0400 (EDT) [thread overview]
Message-ID: <20210824183419.28A5143EF4@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
_Testing issues_
Branch: dpdk-next-net
4f914d656b427c621c3757c23fca7ed9de8ffe79 --> 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.34s
86/94 DPDK:fast-tests / trace_autotest OK 0.40s
87/94 DPDK:fast-tests / telemetry_json_autotest OK 0.48s
88/94 DPDK:fast-tests / telemetry_data_autotest OK 0.45s
89/94 DPDK:fast-tests / ring_pmd_autotest OK 0.34s
90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.42s
91/94 DPDK:fast-tests / bitratestats_autotest OK 0.28s
92/94 DPDK:fast-tests / latencystats_autotest OK 0.32s
93/94 DPDK:fast-tests / pdump_autotest OK 5.43s
94/94 DPDK:fast-tests / compressdev_autotest SKIP 0.46s exit status 77
Ok: 87
Expected Fail: 0
Fail: 3
Unexpected Pass: 0
Skipped: 4
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Arm-gigabyte-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/tarballs/16361/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-08-24 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210824183419.28A5143EF4@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--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).