From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Luc Pelletier <lucp.at.work@gmail.com>
Subject: |FAILURE| pw105877 [PATCH] [v3] eal: fix unaligned loads/stores in rte_memcpy_generic
Date: Sun, 16 Jan 2022 09:38:44 -0500 (EST) [thread overview]
Message-ID: <20220116143844.063646D417@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: FAILURE
http://dpdk.org/patch/105877
_Functional Testing issues_
Submitter: Luc Pelletier <lucp.at.work@gmail.com>
Date: Sunday, January 16 2022 14:13:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f716880ee53ac1e50c9c75dc749886e3257bb8f
105877 --> functional testing fail
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 2/3
Failed Tests:
- mtu_update
- unit_tests_mbuf
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20675/
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-16 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 14:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-16 15:41 dpdklab
[not found] <20220116141304.474374-1-lucp.at.work@gmail.com>
2022-01-16 15:39 ` |FAILURE| pw105877 [PATCH v3] " 0-day Robot
2022-01-16 14:47 |FAILURE| pw105877 [PATCH] [v3] " dpdklab
2022-01-16 14:37 dpdklab
2022-01-16 14:36 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=20220116143844.063646D417@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=lucp.at.work@gmail.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).