automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132886 [PATCH] bitops: mark new symbols as stable
Date: Thu, 19 Oct 2023 02:51:33 -0700 (PDT)	[thread overview]
Message-ID: <6530fc25.050a0220.23f91.f404SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, October 18 2023 09:11:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d7b8b11866a7c4b5975eaedd15dcc9a6f0cd92ce

132886 --> testing pass

Test environment and result as below:

+-----------------+---------------------------+------------------------------+
|   Environment   | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+=================+===========================+==============================+
| Debian 11 (arm) | PASS                      | PASS                         |
+-----------------+---------------------------+------------------------------+


Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-19  9:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  9:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-19 11:39 dpdklab
2023-10-19 10:54 dpdklab
2023-10-19 10:53 dpdklab
2023-10-19 10:49 dpdklab
2023-10-19 10:47 dpdklab
2023-10-19 10:45 dpdklab
2023-10-19 10:38 dpdklab
2023-10-19 10:37 dpdklab
2023-10-19 10:36 dpdklab
2023-10-19 10:36 dpdklab
2023-10-19 10:35 dpdklab
2023-10-19 10:33 dpdklab
2023-10-19 10:31 dpdklab
2023-10-19 10:31 dpdklab
2023-10-19 10:11 dpdklab
2023-10-19 10:10 dpdklab
2023-10-19 10:08 dpdklab
2023-10-19 10:07 dpdklab
2023-10-19 10:03 dpdklab
2023-10-19 10:02 dpdklab
2023-10-19  9:53 dpdklab
2023-10-19  9:53 dpdklab
2023-10-19  9:51 dpdklab
2023-10-19  9:51 dpdklab
2023-10-19  9:51 dpdklab
2023-10-19  9:51 dpdklab
2023-10-19  9:48 dpdklab
2023-10-19  9:47 dpdklab
2023-10-19  9:41 dpdklab
2023-10-19  9:40 dpdklab
2023-10-19  9:38 dpdklab
2023-10-19  9:37 dpdklab
2023-10-19  9:36 dpdklab
2023-10-19  9:36 dpdklab
2023-10-19  9:35 dpdklab
2023-10-19  9:34 dpdklab
2023-10-19  9:17 dpdklab
2023-10-19  8:38 dpdklab
2023-10-19  8:26 dpdklab
2023-10-19  8:06 dpdklab
2023-10-19  8:00 dpdklab
2023-10-19  7:59 dpdklab
2023-10-19  7:55 dpdklab
2023-10-19  7:26 dpdklab
2023-10-19  7:26 dpdklab
2023-10-19  7:22 dpdklab
2023-10-19  7:21 dpdklab
2023-10-19  6:46 dpdklab
2023-10-19  6:37 dpdklab
     [not found] <20231018091123.1594324-1-david.marchand@redhat.com>
2023-10-18  9:07 ` qemudev
2023-10-18  9:11 ` qemudev
2023-10-18  9:13 ` checkpatch
2023-10-18 10:39 ` 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=6530fc25.050a0220.23f91.f404SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.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).