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: [dpdk-test-report] |SUCCESS| pw61077 [PATCH] examples/vm_power: fix build
Date: Mon, 14 Oct 2019 06:35:17 -0400 (EDT)	[thread overview]
Message-ID: <20191014103517.7B7476D557@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

Test-Label: iol-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/61077

_Compile Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Monday, October 14 2019 10:03:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:31b798a6f08e9b333b94b8bb26910209aa810b73

61077 --> compile testing pass

Test environment and result as below:

+--------------+------------------+-------------------+--------------+
| Environment  | dpdk_compile_ovs | dpdk_compile_spdk | dpdk_compile |
+==============+==================+===================+==============+
| Ubuntu 18.04 | PASS             | PASS              | PASS         |
+--------------+------------------+-------------------+--------------+
| FreeBSD 11.2 |                  | PASS              | PASS         |
+--------------+------------------+-------------------+--------------+

Ubuntu 18.04
	Kernel: 4.15.0-generic
	GCC: 7.4

FreeBSD 11.2
	Kernel: 11.2
	GCC: 8.3

https://lab.dpdk.org/results/dashboard/patchsets/7916/

UNH-IOL DPDK Performance Test Lab

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

             reply	other threads:[~2019-10-14 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 10:35 dpdklab [this message]
2019-10-14 10:41 dpdklab
2019-10-14 12:21 dpdklab
     [not found] <20191014100350.30226-1-ferruh.yigit@intel.com>
2019-10-15 15:45 ` checkpatch

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=20191014103517.7B7476D557@noxus.dpdklab.iol.unh.edu \
    --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).