From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Kaiwen Deng <kaiwenx.deng@intel.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128389 [PATCH] net/bonding: fix iavf bond device query s
Date: Thu, 08 Jun 2023 12:55:04 -0700 (PDT) [thread overview]
Message-ID: <64823218.a70a0220.df6f3.399eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128389
_Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Thursday, June 08 2023 07:26:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:55ead98d1de1b02fa563e822a67c7adc0361ddfb
128389 --> testing pass
Test environment and result as below:
+-----------------------------+----------------+--------------+------------------------------+---------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+=============================+================+==============+==============================+===========================+
| (32-bit) ARM Ubuntu 20.04.4 | PASS | SKIPPED | SKIPPED | SKIPPED |
+-----------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS | SKIPPED | SKIPPED |
+-----------------------------+----------------+--------------+------------------------------+---------------------------+
| Debian 11 | SKIPPED | SKIPPED | PASS | PASS |
+-----------------------------+----------------+--------------+------------------------------+---------------------------+
(32-bit) ARM Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26589/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-08 19:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 19:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:05 dpdklab
2023-06-09 4:53 dpdklab
2023-06-09 4:21 dpdklab
2023-06-09 4:13 dpdklab
2023-06-09 4:08 dpdklab
2023-06-09 3:53 dpdklab
2023-06-09 3:05 dpdklab
2023-06-09 3:04 dpdklab
2023-06-09 0:52 dpdklab
2023-06-08 22:41 dpdklab
2023-06-08 20:07 dpdklab
2023-06-08 20:07 dpdklab
2023-06-08 20:07 dpdklab
2023-06-08 20:06 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 20:01 dpdklab
2023-06-08 20:01 dpdklab
2023-06-08 20:01 dpdklab
2023-06-08 20:00 dpdklab
2023-06-08 20:00 dpdklab
2023-06-08 20:00 dpdklab
2023-06-08 20:00 dpdklab
2023-06-08 19:59 dpdklab
2023-06-08 19:58 dpdklab
2023-06-08 19:20 dpdklab
2023-06-08 19:04 dpdklab
2023-06-08 18:30 dpdklab
2023-06-08 18:25 dpdklab
2023-06-08 18:25 dpdklab
2023-06-08 18:25 dpdklab
2023-06-08 18:24 dpdklab
2023-06-08 18:13 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=64823218.a70a0220.df6f3.399eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=kaiwenx.deng@intel.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).