automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw125848 [PATCH] [v2] net: fix return type of IPv6 L4 packet checksum
Date: Thu,  6 Apr 2023 22:03:15 +0000 (UTC)	[thread overview]
Message-ID: <20230406220315.933FC60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125848

_Functional Testing PASS_

Submitter: Elena Agostini <eagostini@nvidia.com>
Date: Thursday, April 06 2023 09:49:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:65487b12db83c9ef37526a983c43191cd44dae99

125848 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25936/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-04-06 22:03 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 22:03 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-07  5:37 dpdklab
2023-04-07  4:43 dpdklab
2023-04-07  4:12 dpdklab
2023-04-07  3:53 dpdklab
2023-04-07  2:16 dpdklab
2023-04-07  2:04 dpdklab
2023-04-07  1:06 dpdklab
2023-04-07  0:32 dpdklab
2023-04-07  0:26 dpdklab
2023-04-07  0:23 dpdklab
2023-04-07  0:21 dpdklab
2023-04-07  0:16 dpdklab
2023-04-07  0:13 dpdklab
2023-04-07  0:10 dpdklab
2023-04-07  0:09 dpdklab
2023-04-07  0:06 dpdklab
2023-04-06 23:59 dpdklab
2023-04-06 23:51 dpdklab
2023-04-06 23:50 dpdklab
2023-04-06 23:38 dpdklab
2023-04-06 23:37 dpdklab
2023-04-06 23:25 dpdklab
2023-04-06 23:24 dpdklab
2023-04-06 23:18 dpdklab
2023-04-06 23:16 dpdklab
2023-04-06 23:13 dpdklab
2023-04-06 23:09 dpdklab
2023-04-06 23:08 dpdklab
2023-04-06 23:08 dpdklab
2023-04-06 23:04 dpdklab
2023-04-06 23:00 dpdklab
2023-04-06 23:00 dpdklab
2023-04-06 23:00 dpdklab
2023-04-06 22:56 dpdklab
2023-04-06 22:55 dpdklab
2023-04-06 22:53 dpdklab
2023-04-06 22:52 dpdklab
2023-04-06 22:51 dpdklab
2023-04-06 22:46 dpdklab
2023-04-06 22:45 dpdklab
2023-04-06 22:23 dpdklab
2023-04-06 22:19 dpdklab
2023-04-06 22:15 dpdklab
2023-04-06 22:12 dpdklab
2023-04-06 22:10 dpdklab
2023-04-06 22:07 dpdklab
2023-04-06 22:07 dpdklab
2023-04-06 22:06 dpdklab
2023-04-06 22:05 dpdklab
2023-04-06 22:04 dpdklab
2023-04-06 21:59 dpdklab
2023-04-06 21:58 dpdklab
     [not found] <20230406094944.821106-1-eagostini@nvidia.com>
2023-04-06  9:42 ` |SUCCESS| pw125848 [PATCH v2] " qemudev
2023-04-06  9:46 ` qemudev
2023-04-06  9:52 ` checkpatch
2023-04-06 11:18 ` 0-day Robot

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=20230406220315.933FC60095@dpdk-ubuntu.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).