From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] b05d183a7f6040a6748eae5717f030e00e30544c
Date: Wed, 26 Jan 2022 12:55:03 +0000 (UTC) [thread overview]
Message-ID: <20220126125503.09FC3601B5@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2394 bytes --]
_Testing issues_
Branch: tags/v20.11
b05d183a7f6040a6748eae5717f030e00e30544c --> testing fail
Test environment and result as below:
+-------------------------------+--------------+----------------+
| Environment | lpm_autotest | dpdk_unit_test |
+===============================+==============+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED |
+-------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM GCC Native | SKIPPED | PASS |
+-------------------------------+--------------+----------------+
| Ubuntu 20.04 ARM Clang Native | SKIPPED | FAIL |
+-------------------------------+--------------+----------------+
==== 20 line log output for Ubuntu 20.04 ARM Clang Native (dpdk_unit_test): ====
85/94 DPDK:fast-tests / thash_autotest OK 0.82s
86/94 DPDK:fast-tests / trace_autotest OK 0.85s
87/94 DPDK:fast-tests / telemetry_json_autotest OK 0.82s
88/94 DPDK:fast-tests / telemetry_data_autotest OK 0.74s
89/94 DPDK:fast-tests / ring_pmd_autotest OK 0.51s
90/94 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.72s
91/94 DPDK:fast-tests / bitratestats_autotest OK 0.49s
92/94 DPDK:fast-tests / latencystats_autotest OK 0.49s
93/94 DPDK:fast-tests / pdump_autotest OK 5.66s
94/94 DPDK:fast-tests / compressdev_autotest SKIP 0.81s 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 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/tarballs/18438/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-01-26 12:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 12:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-21 7:46 dpdklab
2022-02-20 11:48 dpdklab
2022-02-20 3:05 dpdklab
2022-02-19 1:44 dpdklab
2022-02-18 9:30 dpdklab
2022-02-17 20:21 dpdklab
2022-02-16 9:17 dpdklab
2022-02-16 3:03 dpdklab
2022-02-15 2:37 dpdklab
2022-02-12 23:11 dpdklab
2022-02-09 0:54 dpdklab
2022-02-07 23:45 dpdklab
2022-02-07 20:43 dpdklab
2022-02-07 18:30 dpdklab
2022-02-07 9:17 dpdklab
2022-02-06 9:56 dpdklab
2022-02-05 9:45 dpdklab
2022-02-03 5:50 dpdklab
2022-02-02 6:42 dpdklab
2022-02-02 5:58 dpdklab
2022-01-27 6:21 dpdklab
2022-01-26 2:08 dpdklab
2022-01-24 6:54 dpdklab
2022-01-22 7:09 dpdklab
2022-01-22 5:59 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=20220126125503.09FC3601B5@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).