From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw86468 [PATCH] [v3, 9/9] eal: probe devices of same PCI but different devargs
Date: Thu, 14 Jan 2021 22:38:10 -0500 (EST) [thread overview]
Message-ID: <20210115033810.D7C9489035@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/86468
_Testing PASS_
Submitter: Xueming Li <xuemingl@nvidia.com>
Date: Wednesday, January 13 2021 13:44:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9b27a37b847237bc7b4f8369e1dad2dce3cdbb44
86468 --> 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/15151/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-01-15 3:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 3:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-15 5:10 dpdklab
2021-01-15 3:38 dpdklab
2021-01-13 15:37 dpdklab
2021-01-13 15:24 dpdklab
2021-01-13 15:18 dpdklab
2021-01-13 15:14 dpdklab
2021-01-13 15:12 dpdklab
2021-01-13 15:03 dpdklab
2021-01-13 15:00 dpdklab
2021-01-13 14:56 dpdklab
[not found] <20210113134422.15723-10-xuemingl@nvidia.com>
2021-01-13 13:47 ` [dpdk-test-report] |SUCCESS| pw86468 [PATCH v3 " 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=20210115033810.D7C9489035@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).