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| pw129698 [PATCH] [v3] dts: update dependencies and mypy ex
Date: Tue, 25 Jul 2023 11:24:59 -0700 (PDT)	[thread overview]
Message-ID: <64c0137b.6b0a0220.56e70.4f38SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-aarch-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129698

_Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Tuesday, July 25 2023 08:48:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5c9f84a868c51c3c9f7913b941594cad2edc9310

129698 --> testing pass

Test environment and result as below:

+-----------------------------+---------------------------+------------------------------+----------------+--------------+
|         Environment         | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test | lpm_autotest |
+=============================+===========================+==============================+================+==============+
| Debian 11                   | PASS                      | PASS                         | SKIPPED        | SKIPPED      |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
| (32-bit) ARM Ubuntu 20.04.4 | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED                   | SKIPPED                      | SKIPPED        | PASS         |
+-----------------------------+---------------------------+------------------------------+----------------+--------------+


Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

(32-bit) ARM Ubuntu 20.04.4
	Kernel: 5.4.0-148-generic aarch64
	Compiler: gcc 9.4

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/27136/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-25 18:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 18:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-25 23:54 dpdklab
2023-07-25 20:08 dpdklab
2023-07-25 19:43 dpdklab
2023-07-25 19:43 dpdklab
2023-07-25 19:19 dpdklab
2023-07-25 19:15 dpdklab
2023-07-25 19:14 dpdklab
2023-07-25 19:12 dpdklab
2023-07-25 19:08 dpdklab
2023-07-25 18:57 dpdklab
2023-07-25 18:43 dpdklab
2023-07-25 18:35 dpdklab
2023-07-25 18:31 dpdklab
2023-07-25 18:25 dpdklab
2023-07-25 18:24 dpdklab
2023-07-25 18:24 dpdklab
2023-07-25 18:23 dpdklab
2023-07-25 18:15 dpdklab
2023-07-25 18:13 dpdklab
2023-07-25 18:09 dpdklab
2023-07-25 18:03 dpdklab
2023-07-25 18:01 dpdklab
2023-07-25 17:58 dpdklab
2023-07-25 17:45 dpdklab
2023-07-25 17:35 dpdklab
2023-07-25 17:29 dpdklab
2023-07-25 17:27 dpdklab
2023-07-25 17:27 dpdklab
2023-07-25 17:27 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=64c0137b.6b0a0220.56e70.4f38SMTPIN_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).