From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw112111 [PATCH] [v10] sched: enable traffic class oversubscription conditionally
Date: Tue, 31 May 2022 06:35:12 -0400 (EDT) [thread overview]
Message-ID: <20220531103512.9F0896D4C2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/112111
_Functional Testing PASS_
Submitter: Marcin Danilewicz <marcinx.danilewicz@intel.com>
Date: Tuesday, May 31 2022 09:49:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:60018ef4d33d5d3e1e9995945ec33a07e75784a4
112111 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/22369/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-05-31 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 10:35 dpdklab [this message]
2022-05-31 10:43 dpdklab
[not found] <20220531094928.842735-1-marcinx.danilewicz@intel.com>
2022-05-31 9:50 ` |SUCCESS| pw112111 [PATCH v10] " checkpatch
2022-05-31 10:47 ` 0-day Robot
2022-05-31 11:29 |SUCCESS| pw112111 [PATCH] [v10] " dpdklab
2022-05-31 11:35 dpdklab
2022-05-31 12:12 dpdklab
2022-05-31 12:35 dpdklab
2022-05-31 12:41 dpdklab
2022-05-31 12:43 dpdklab
2022-06-01 7:22 dpdklab
2022-06-01 7:38 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=20220531103512.9F0896D4C2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).