automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw76612 [PATCH] crypto/dpaax_sec: fix a null pointer dereference after null check
Date: Sat,  5 Sep 2020 07:53:49 -0400 (EDT)	[thread overview]
Message-ID: <20200905115349.C1B27510@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/76612

_Functional Testing PASS_

Submitter: wangyunjian <wangyunjian@huawei.com>
Date: Saturday, September 05 2020 10:26:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd6f1d7a5fde76c4f1e771de9f7aafdf59d691e4

76612 --> functional testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-09-05 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 11:53 dpdklab [this message]
     [not found] <f1965d60316035dc1914b2a21b8ad238190f64da.1599301379.git.wangyunjian@huawei.com>
2020-09-08 23:45 ` checkpatch
  -- strict thread matches above, loose matches on Subject: below --
2020-09-05 14:13 dpdklab
2020-09-05 13:20 dpdklab
2020-09-05 13:01 dpdklab
2020-09-05 12:27 dpdklab
2020-09-05 11:43 dpdklab
2020-09-05 11:30 dpdklab
2020-09-05 11:20 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=20200905115349.C1B27510@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --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).