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| pw132603-132604 [PATCH] [v4,2/2] dts: reformat to 100 line
Date: Fri, 13 Oct 2023 06:19:56 -0700 (PDT)	[thread overview]
Message-ID: <652943fc.170a0220.da76a.84e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132604

_Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Friday, October 13 2023 07:58:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:77f913752a55c0262bfda99a1b69ca0bd804c6c7

132603-132604 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

UNH-IOL DPDK Community Lab

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

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

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 13:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-13 15:19 dpdklab
2023-10-13 13:54 dpdklab
2023-10-13 13:53 dpdklab
2023-10-13 13:46 dpdklab
2023-10-13 13:31 dpdklab
2023-10-13 13:31 dpdklab
2023-10-13 13:31 dpdklab
2023-10-13 13:23 dpdklab
2023-10-13 13:22 dpdklab
2023-10-13 13:21 dpdklab
2023-10-13 13:18 dpdklab
2023-10-13 13:16 dpdklab
2023-10-13 13:15 dpdklab
2023-10-13 13:14 dpdklab
2023-10-13 13:12 dpdklab
2023-10-13 13:11 dpdklab
2023-10-13 13:05 dpdklab
2023-10-13 13:05 dpdklab
2023-10-13 12:58 dpdklab
2023-10-13 12:57 dpdklab
2023-10-13 12:56 dpdklab
2023-10-13 12:49 dpdklab
2023-10-13 12:48 dpdklab
2023-10-13 12:45 dpdklab
2023-10-13 12:43 dpdklab
2023-10-13 12:41 dpdklab
2023-10-13 12:41 dpdklab
2023-10-13 12:40 dpdklab
2023-10-13 12:39 dpdklab
2023-10-13 12:39 dpdklab
2023-10-13 12:38 dpdklab
2023-10-13 12:38 dpdklab
2023-10-13 12:37 dpdklab
2023-10-13 12:37 dpdklab
2023-10-13 12:36 dpdklab
2023-10-13 12:36 dpdklab
2023-10-13 12:30 dpdklab
2023-10-13 12:30 dpdklab
2023-10-13 12:30 dpdklab
2023-10-13 12:26 dpdklab
2023-10-13 12:24 dpdklab
2023-10-13 12:15 dpdklab
2023-10-13 12:15 dpdklab
2023-10-13 12:15 dpdklab
2023-10-13 12:13 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=652943fc.170a0220.da76a.84e4SMTPIN_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).