From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132453-132454 [PATCH] [2/2] net/nfp: fix illegal memory
Date: Tue, 10 Oct 2023 11:02:51 -0700 (PDT) [thread overview]
Message-ID: <652591cb.630a0220.25aef.3f35SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132454
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, October 10 2023 06:17:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132453-132454 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27876/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-10 18:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 18:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 0:02 dpdklab
2023-10-11 23:58 dpdklab
2023-10-11 23:46 dpdklab
2023-10-11 23:41 dpdklab
2023-10-11 21:08 dpdklab
2023-10-10 23:29 dpdklab
2023-10-10 23:05 dpdklab
2023-10-10 22:33 dpdklab
2023-10-10 22:32 dpdklab
2023-10-10 22:28 dpdklab
2023-10-10 21:33 dpdklab
2023-10-10 21:33 dpdklab
2023-10-10 21:29 dpdklab
2023-10-10 21:29 dpdklab
2023-10-10 21:28 dpdklab
2023-10-10 21:28 dpdklab
2023-10-10 21:28 dpdklab
2023-10-10 21:24 dpdklab
2023-10-10 21:23 dpdklab
2023-10-10 21:22 dpdklab
2023-10-10 21:22 dpdklab
2023-10-10 21:22 dpdklab
2023-10-10 21:21 dpdklab
2023-10-10 21:19 dpdklab
2023-10-10 21:18 dpdklab
2023-10-10 21:18 dpdklab
2023-10-10 21:17 dpdklab
2023-10-10 21:16 dpdklab
2023-10-10 21:15 dpdklab
2023-10-10 21:15 dpdklab
2023-10-10 21:11 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:08 dpdklab
2023-10-10 18:54 dpdklab
2023-10-10 18:47 dpdklab
2023-10-10 18:43 dpdklab
2023-10-10 18:17 dpdklab
2023-10-10 18:03 dpdklab
2023-10-10 17:57 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=652591cb.630a0220.25aef.3f35SMTPIN_ADDED_MISSING@mx.google.com \
--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).