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| pw136604-136617 [PATCH] [15/15] vhost: use GCC and MSVC co
Date: Mon, 12 Feb 2024 15:57:45 -0800 (PST)	[thread overview]
Message-ID: <65cab079.050a0220.f065e.b68dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136617

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, February 12 2024 21:49:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39fbd379aa448fda098575f6052dfcdf1dc8e23b

136604-136617 --> 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               |
+----------------------+--------------------+


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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-12 23:57 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 23:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-13  1:19 dpdklab
2024-02-13  1:18 dpdklab
2024-02-13  1:15 dpdklab
2024-02-13  1:03 dpdklab
2024-02-13  0:54 dpdklab
2024-02-13  0:51 dpdklab
2024-02-13  0:43 dpdklab
2024-02-13  0:38 dpdklab
2024-02-13  0:36 dpdklab
2024-02-13  0:32 dpdklab
2024-02-13  0:28 dpdklab
2024-02-13  0:28 dpdklab
2024-02-13  0:27 dpdklab
2024-02-13  0:26 dpdklab
2024-02-13  0:24 dpdklab
2024-02-13  0:23 dpdklab
2024-02-13  0:23 dpdklab
2024-02-13  0:22 dpdklab
2024-02-13  0:22 dpdklab
2024-02-13  0:22 dpdklab
2024-02-13  0:21 dpdklab
2024-02-13  0:21 dpdklab
2024-02-13  0:20 dpdklab
2024-02-13  0:20 dpdklab
2024-02-13  0:20 dpdklab
2024-02-13  0:20 dpdklab
2024-02-13  0:20 dpdklab
2024-02-13  0:19 dpdklab
2024-02-13  0:18 dpdklab
2024-02-13  0:18 dpdklab
2024-02-13  0:15 dpdklab
2024-02-13  0:15 dpdklab
2024-02-13  0:13 dpdklab
2024-02-13  0:12 dpdklab
2024-02-13  0:11 dpdklab
2024-02-13  0:10 dpdklab
2024-02-13  0:08 dpdklab
2024-02-13  0:07 dpdklab
2024-02-13  0:06 dpdklab
2024-02-13  0:06 dpdklab
2024-02-13  0:06 dpdklab
2024-02-13  0:04 dpdklab
2024-02-13  0:04 dpdklab
2024-02-13  0:04 dpdklab
2024-02-13  0:02 dpdklab
2024-02-13  0:02 dpdklab
2024-02-13  0:00 dpdklab
2024-02-12 23:59 dpdklab
2024-02-12 23:58 dpdklab
2024-02-12 23:57 dpdklab
2024-02-12 23:56 dpdklab
2024-02-12 23:55 dpdklab
2024-02-12 23:55 dpdklab
2024-02-12 23:54 dpdklab
2024-02-12 23:53 dpdklab
2024-02-12 23:53 dpdklab
2024-02-12 23:52 dpdklab
2024-02-12 23:52 dpdklab
2024-02-12 23:52 dpdklab
2024-02-12 23:51 dpdklab
2024-02-12 23:51 dpdklab
2024-02-12 23:50 dpdklab
2024-02-12 23:50 dpdklab
2024-02-12 23:50 dpdklab
2024-02-12 23:49 dpdklab
2024-02-12 23:49 dpdklab
2024-02-12 23:48 dpdklab
2024-02-12 23:45 dpdklab
2024-02-12 23:34 dpdklab
2024-02-12 23:33 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=65cab079.050a0220.f065e.b68dSMTPIN_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).