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
Subject: |SUCCESS| pw127138 [PATCH] test/mbuf: fix the forked process segment
Date: Mon, 22 May 2023 00:05:48 -0700 (PDT)	[thread overview]
Message-ID: <646b144c.9d0a0220.b0b33.6eb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/127138

_Testing PASS_

Submitter: Ruifeng Wang <ruifeng.wang@arm.com>
Date: Monday, May 22 2023 06:01:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

127138 --> testing pass

Test environment and result as below:

+----------------------+---------------------------+------------------------------+--------------+
|     Environment      | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11            | PASS                      | PASS                         | SKIPPED      |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED                   | SKIPPED                      | PASS         |
+----------------------+---------------------------+------------------------------+--------------+


Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-22  7:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  7:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-22  7:56 dpdklab
2023-05-22  7:40 dpdklab
2023-05-22  7:28 dpdklab
2023-05-22  7:26 dpdklab
2023-05-22  7:24 dpdklab
2023-05-22  7:24 dpdklab
2023-05-22  7:21 dpdklab
2023-05-22  7:16 dpdklab
2023-05-22  7:16 dpdklab
2023-05-22  7:13 dpdklab
2023-05-22  7:12 dpdklab
2023-05-22  7:10 dpdklab
2023-05-22  7:07 dpdklab
2023-05-22  7:04 dpdklab
2023-05-22  7:03 dpdklab
2023-05-22  6:58 dpdklab
2023-05-22  6:55 dpdklab
2023-05-22  6:50 dpdklab
2023-05-22  6:46 dpdklab
2023-05-22  6:46 dpdklab
2023-05-22  6:46 dpdklab
2023-05-22  6:41 dpdklab
2023-05-22  6:39 dpdklab
2023-05-22  6:39 dpdklab
2023-05-22  6:38 dpdklab
2023-05-22  6:34 dpdklab
2023-05-22  6:33 dpdklab
2023-05-22  6:30 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=646b144c.9d0a0220.b0b33.6eb6SMTPIN_ADDED_MISSING@mx.google.com \
    --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).