automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw135334 [PATCH] kernel/freebsd: fix module build on FreeB
Date: Tue, 19 Dec 2023 08:45:32 -0800 (PST)	[thread overview]
Message-ID: <6581c8ac.050a0220.1f406.b7acSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, December 19 2023 11:29:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135334 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| Debian Buster   | PASS     |
+-----------------+----------+


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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-19 16:45 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 16:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 19:33 dpdklab
2023-12-19 18:17 dpdklab
2023-12-19 18:17 dpdklab
2023-12-19 17:51 dpdklab
2023-12-19 17:50 dpdklab
2023-12-19 17:40 dpdklab
2023-12-19 17:27 dpdklab
2023-12-19 17:26 dpdklab
2023-12-19 17:26 dpdklab
2023-12-19 17:24 dpdklab
2023-12-19 17:23 dpdklab
2023-12-19 17:22 dpdklab
2023-12-19 17:22 dpdklab
2023-12-19 17:21 dpdklab
2023-12-19 17:20 dpdklab
2023-12-19 17:18 dpdklab
2023-12-19 17:18 dpdklab
2023-12-19 17:17 dpdklab
2023-12-19 17:17 dpdklab
2023-12-19 17:17 dpdklab
2023-12-19 17:14 dpdklab
2023-12-19 17:12 dpdklab
2023-12-19 17:10 dpdklab
2023-12-19 17:10 dpdklab
2023-12-19 17:09 dpdklab
2023-12-19 17:09 dpdklab
2023-12-19 17:09 dpdklab
2023-12-19 17:08 dpdklab
2023-12-19 17:06 dpdklab
2023-12-19 17:06 dpdklab
2023-12-19 17:03 dpdklab
2023-12-19 17:02 dpdklab
2023-12-19 17:01 dpdklab
2023-12-19 17:00 dpdklab
2023-12-19 16:59 dpdklab
2023-12-19 16:59 dpdklab
2023-12-19 16:59 dpdklab
2023-12-19 16:58 dpdklab
2023-12-19 16:58 dpdklab
2023-12-19 16:56 dpdklab
2023-12-19 16:54 dpdklab
2023-12-19 16:54 dpdklab
2023-12-19 16:53 dpdklab
2023-12-19 16:48 dpdklab
2023-12-19 16:48 dpdklab
2023-12-19 16:46 dpdklab
2023-12-19 16:45 dpdklab
2023-12-19 16:45 dpdklab
2023-12-19 16:44 dpdklab
2023-12-19 16:43 dpdklab
2023-12-19 16:42 dpdklab
2023-12-19 16:42 dpdklab
2023-12-19 16:41 dpdklab
2023-12-19 16:41 dpdklab
2023-12-19 16:41 dpdklab
2023-12-19 16:40 dpdklab
2023-12-19 16:39 dpdklab
2023-12-19 16:37 dpdklab
2023-12-19 16:35 dpdklab
2023-12-19 16:34 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:31 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=6581c8ac.050a0220.1f406.b7acSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --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).