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| pw132751 [PATCH] event/cnxk: fix symbol map
Date: Tue, 17 Oct 2023 14:53:14 -0700 (PDT)	[thread overview]
Message-ID: <652f024a.5d0a0220.57372.61c9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132751

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, October 17 2023 12:35:59 
DPDK git baseline: Repo:dpdk-next-eventdev
  Branch: master
  CommitID:4aa8315ee12e17785588fb9891306b9dee685d6b

132751 --> testing pass

Test environment and result as below:

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


Debian 11 (arm)
	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/27968/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-17 21:53 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 21:53 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 21:54 dpdklab
2023-10-18  1:03 dpdklab
2023-10-17 23:12 dpdklab
2023-10-17 22:14 dpdklab
2023-10-17 22:04 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:55 dpdklab
2023-10-17 21:53 dpdklab
2023-10-17 21:52 dpdklab
2023-10-17 21:52 dpdklab
2023-10-17 21:52 dpdklab
2023-10-17 21:51 dpdklab
2023-10-17 21:51 dpdklab
2023-10-17 21:49 dpdklab
2023-10-17 21:48 dpdklab
2023-10-17 21:48 dpdklab
2023-10-17 21:48 dpdklab
2023-10-17 21:48 dpdklab
2023-10-17 21:47 dpdklab
2023-10-17 21:47 dpdklab
2023-10-17 21:46 dpdklab
2023-10-17 21:46 dpdklab
2023-10-17 21:46 dpdklab
2023-10-17 21:46 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 21:45 dpdklab
2023-10-17 21:44 dpdklab
2023-10-17 21:44 dpdklab
2023-10-17 20:22 dpdklab
2023-10-17 20:11 dpdklab
2023-10-17 20:04 dpdklab
2023-10-17 18:53 dpdklab
2023-10-17 18:49 dpdklab
2023-10-17 18:46 dpdklab
2023-10-17 18:41 dpdklab
     [not found] <20231017123600.3189269-1-david.marchand@redhat.com>
2023-10-17 12:17 ` qemudev
2023-10-17 12:22 ` qemudev
2023-10-17 12:36 ` checkpatch

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=652f024a.5d0a0220.57372.61c9SMTPIN_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).