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| pw64678 [PATCH] net/ixgbe: fix build for gcc 4.8.5
Date: Tue, 14 Jan 2020 17:47:45 -0500 (EST)	[thread overview]
Message-ID: <20200114224745.8D6DCA7A2@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/64678

_Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tuesday, January 14 2020 17:52:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a02b9406a8769247737b55dbfa50b6b5f896d946

64678 --> testing pass

Test environment and result as below:

+------------------+-------------------+--------------------+--------------+------------------+----------------+
|   Environment    | dpdk_compile_spdk | dpdk_meson_compile | dpdk_compile | dpdk_compile_ovs | dpdk_unit_test |
+==================+===================+====================+==============+==================+================+
| FreeBSD 11.2     | PASS              | PASS               | PASS         | SKIPPED          | SKIPPED        |
+------------------+-------------------+--------------------+--------------+------------------+----------------+
| Ubuntu 18.04     | PASS              | PASS               | PASS         | PASS             | PASS           |
+------------------+-------------------+--------------------+--------------+------------------+----------------+
| openSUSE Leap 15 | SKIPPED           | PASS               | PASS         | PASS             | SKIPPED        |
+------------------+-------------------+--------------------+--------------+------------------+----------------+
| Fedora 31        | SKIPPED           | PASS               | PASS         | PASS             | SKIPPED        |
+------------------+-------------------+--------------------+--------------+------------------+----------------+
| CentOS 8         | SKIPPED           | PASS               | PASS         | PASS             | SKIPPED        |
+------------------+-------------------+--------------------+--------------+------------------+----------------+
| Arch Linux       | SKIPPED           | PASS               | PASS         | PASS             | SKIPPED        |
+------------------+-------------------+--------------------+--------------+------------------+----------------+

FreeBSD 11.2
	Kernel: 11.2
	GCC: 8.3

Ubuntu 18.04
	Kernel: 4.15.0-generic
	GCC: 7.4

openSUSE Leap 15
	Kernel: 4.12.14
	GCC: 7.4.1

Fedora 31
	Kernel: 5.3.16
	GCC: 9.2.1

CentOS 8
	Kernel: 4.18.0.el8_0
	GCC: 8.2

Arch Linux
	Kernel: latest
	GCC: latest

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-01-14 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 22:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-15  0:08 dpdklab
2020-01-15  0:08 dpdklab
2020-01-14 22:40 dpdklab
     [not found] <20200114175247.2930261-1-ferruh.yigit@intel.com>
2020-01-14 17:53 ` 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=20200114224745.8D6DCA7A2@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).