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| pw136378-136379 [PATCH] [2/2] rcu: use correct value of ac
Date: Sun, 04 Feb 2024 22:38:36 -0800 (PST)	[thread overview]
Message-ID: <65c0826c.050a0220.14834.d9d1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Date: Monday, February 05 2024 04:59:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b

136378-136379 --> testing pass

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+


CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-05  6:38 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  6:38 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-05 10:04 dpdklab
2024-02-05  9:31 dpdklab
2024-02-05  8:16 dpdklab
2024-02-05  8:11 dpdklab
2024-02-05  7:58 dpdklab
2024-02-05  7:49 dpdklab
2024-02-05  7:23 dpdklab
2024-02-05  7:20 dpdklab
2024-02-05  7:19 dpdklab
2024-02-05  7:16 dpdklab
2024-02-05  7:14 dpdklab
2024-02-05  7:14 dpdklab
2024-02-05  7:13 dpdklab
2024-02-05  7:13 dpdklab
2024-02-05  7:11 dpdklab
2024-02-05  7:10 dpdklab
2024-02-05  7:09 dpdklab
2024-02-05  7:09 dpdklab
2024-02-05  7:08 dpdklab
2024-02-05  7:08 dpdklab
2024-02-05  7:08 dpdklab
2024-02-05  7:07 dpdklab
2024-02-05  7:07 dpdklab
2024-02-05  7:04 dpdklab
2024-02-05  7:04 dpdklab
2024-02-05  7:04 dpdklab
2024-02-05  7:03 dpdklab
2024-02-05  7:03 dpdklab
2024-02-05  7:02 dpdklab
2024-02-05  7:02 dpdklab
2024-02-05  7:01 dpdklab
2024-02-05  7:01 dpdklab
2024-02-05  7:01 dpdklab
2024-02-05  7:00 dpdklab
2024-02-05  7:00 dpdklab
2024-02-05  7:00 dpdklab
2024-02-05  6:59 dpdklab
2024-02-05  6:59 dpdklab
2024-02-05  6:58 dpdklab
2024-02-05  6:58 dpdklab
2024-02-05  6:58 dpdklab
2024-02-05  6:58 dpdklab
2024-02-05  6:57 dpdklab
2024-02-05  6:56 dpdklab
2024-02-05  6:54 dpdklab
2024-02-05  6:53 dpdklab
2024-02-05  6:51 dpdklab
2024-02-05  6:50 dpdklab
2024-02-05  6:49 dpdklab
2024-02-05  6:47 dpdklab
2024-02-05  6:38 dpdklab
2024-02-05  6:38 dpdklab
2024-02-05  6:38 dpdklab
2024-02-05  6:38 dpdklab
2024-02-05  6:38 dpdklab
2024-02-05  6:34 dpdklab
2024-02-05  6:34 dpdklab
2024-02-05  6:33 dpdklab
2024-02-05  6:32 dpdklab
2024-02-05  6:31 dpdklab
2024-02-05  6:31 dpdklab
2024-02-05  6:31 dpdklab
2024-02-05  6:31 dpdklab
2024-02-05  6:29 dpdklab
2024-02-05  6:24 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=65c0826c.050a0220.14834.d9d1SMTPIN_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).