From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136283 [PATCH] [v3] doc: update guideline for fix commit
Date: Thu, 01 Feb 2024 07:49:25 -0800 (PST) [thread overview]
Message-ID: <65bbbd85.630a0220.6488e.20aaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136283
_Testing PASS_
Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Thursday, February 01 2024 13:48:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3178e37c65a676366f33f0bc56f49d9b26a06448
136283 --> testing pass
Test environment and result as below:
+-----------------------+--------------------+
| Environment | dpdk_meson_compile |
+=======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+-----------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+-----------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+-----------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+-----------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29017/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 15:49 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 15:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 18:26 dpdklab
2024-02-01 17:51 dpdklab
2024-02-01 17:20 dpdklab
2024-02-01 17:20 dpdklab
2024-02-01 16:48 dpdklab
2024-02-01 16:33 dpdklab
2024-02-01 16:32 dpdklab
2024-02-01 16:31 dpdklab
2024-02-01 16:25 dpdklab
2024-02-01 16:23 dpdklab
2024-02-01 16:20 dpdklab
2024-02-01 16:12 dpdklab
2024-02-01 16:09 dpdklab
2024-02-01 16:03 dpdklab
2024-02-01 16:02 dpdklab
2024-02-01 16:00 dpdklab
2024-02-01 15:59 dpdklab
2024-02-01 15:57 dpdklab
2024-02-01 15:57 dpdklab
2024-02-01 15:55 dpdklab
2024-02-01 15:53 dpdklab
2024-02-01 15:53 dpdklab
2024-02-01 15:53 dpdklab
2024-02-01 15:52 dpdklab
2024-02-01 15:52 dpdklab
2024-02-01 15:51 dpdklab
2024-02-01 15:51 dpdklab
2024-02-01 15:50 dpdklab
2024-02-01 15:47 dpdklab
2024-02-01 15:46 dpdklab
2024-02-01 15:46 dpdklab
2024-02-01 15:45 dpdklab
2024-02-01 15:45 dpdklab
2024-02-01 15:45 dpdklab
2024-02-01 15:44 dpdklab
2024-02-01 15:43 dpdklab
2024-02-01 15:42 dpdklab
2024-02-01 15:40 dpdklab
2024-02-01 15:40 dpdklab
2024-02-01 15:39 dpdklab
2024-02-01 15:38 dpdklab
2024-02-01 15:38 dpdklab
2024-02-01 15:35 dpdklab
2024-02-01 15:35 dpdklab
2024-02-01 15:34 dpdklab
2024-02-01 15:33 dpdklab
2024-02-01 15:33 dpdklab
2024-02-01 15:32 dpdklab
2024-02-01 15:30 dpdklab
2024-02-01 15:26 dpdklab
2024-02-01 15:25 dpdklab
2024-02-01 15:21 dpdklab
2024-02-01 15:21 dpdklab
2024-02-01 15:19 dpdklab
2024-02-01 15:16 dpdklab
2024-02-01 15:15 dpdklab
2024-02-01 15:14 dpdklab
2024-02-01 15:13 dpdklab
2024-02-01 15:12 dpdklab
2024-02-01 15:12 dpdklab
2024-02-01 15:11 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:10 dpdklab
2024-02-01 15:09 dpdklab
2024-02-01 15:08 dpdklab
2024-02-01 15:07 dpdklab
2024-02-01 14:59 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=65bbbd85.630a0220.6488e.20aaSMTPIN_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).