automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jieqiang Wang <jieqiang.wang@arm.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131183 [PATCH] hash: fix SSE comparison
Date: Tue, 05 Sep 2023 20:26:55 -0700 (PDT)	[thread overview]
Message-ID: <64f7f17f.050a0220.a84a4.5a67SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Jieqiang Wang <jieqiang.wang@arm.com>
Date: Wednesday, September 06 2023 02:31:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e92ba1426914db1d224dd5e9a1743657681b8814

131183 --> 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/27531/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-06  3:26 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  3:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-06  7:37 dpdklab
2023-09-06  7:32 dpdklab
2023-09-06  7:27 dpdklab
2023-09-06  7:23 dpdklab
2023-09-06  4:51 dpdklab
2023-09-06  4:31 dpdklab
2023-09-06  4:25 dpdklab
2023-09-06  4:03 dpdklab
2023-09-06  4:02 dpdklab
2023-09-06  3:57 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:56 dpdklab
2023-09-06  3:55 dpdklab
2023-09-06  3:55 dpdklab
2023-09-06  3:51 dpdklab
2023-09-06  3:50 dpdklab
2023-09-06  3:50 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:42 dpdklab
2023-09-06  3:38 dpdklab
2023-09-06  3:35 dpdklab
2023-09-06  3:34 dpdklab
2023-09-06  3:33 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:32 dpdklab
2023-09-06  3:31 dpdklab
2023-09-06  3:31 dpdklab
2023-09-06  3:28 dpdklab
2023-09-06  3:28 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:27 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:26 dpdklab
2023-09-06  3:25 dpdklab
2023-09-06  3:23 dpdklab
2023-09-06  3:23 dpdklab
2023-09-06  3:22 dpdklab
2023-09-06  3:22 dpdklab
2023-09-06  3:21 dpdklab
2023-09-06  3:20 dpdklab
2023-09-06  3:20 dpdklab
2023-09-06  3:20 dpdklab
     [not found] <20230906023100.3618303-1-jieqiang.wang@arm.com>
2023-09-06  2:18 ` qemudev
2023-09-06  2:22 ` qemudev
2023-09-06  2:32 ` checkpatch
2023-09-06  3:19 ` 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=64f7f17f.050a0220.a84a4.5a67SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jieqiang.wang@arm.com \
    --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).