From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw88128 [PATCH] [v2] net/mlx5: fix hashed list size for tunnel flow groups
Date: Wed, 24 Feb 2021 04:33:30 -0500 (EST) [thread overview]
Message-ID: <20210224093330.E03516D44A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/88128
_Testing PASS_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Wednesday, February 24 2021 08:15:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:51fe32138c860992f228dbf19416ffd3b8e8baf4
88128 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 18.04 | PASS |
+------------------+----------+
| Ubuntu 18.04 ARM | PASS |
+------------------+----------+
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.5
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15702/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-02-24 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 9:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-24 11:56 dpdklab
2021-02-24 10:36 dpdklab
2021-02-24 9:48 dpdklab
2021-02-24 9:35 dpdklab
2021-02-24 9:18 dpdklab
2021-02-24 9:14 dpdklab
2021-02-24 9:02 dpdklab
2021-02-24 8:59 dpdklab
2021-02-24 8:58 dpdklab
2021-02-24 8:45 dpdklab
[not found] <20210224081514.56826-1-viacheslavo@nvidia.com>
2021-02-24 8:15 ` [dpdk-test-report] |SUCCESS| pw88128 [PATCH v2] " checkpatch
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=20210224093330.E03516D44A@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).