From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140027 [PATCH] bpf: don't verify classic bpfs
Date: Mon, 13 May 2024 05:01:17 -0700 (PDT) [thread overview]
Message-ID: <6642010d.050a0220.fa3fc.c6c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240512060041.100723-1-yoav.w@claroty.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/140027
_Functional Testing PASS_
Submitter: Yoav Winstein <yoav.w@claroty.com>
Date: Sunday, May 12 2024 06:00:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
140027 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29943/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-05-13 12:01 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240512060041.100723-1-yoav.w@claroty.com>
2024-05-12 5:41 ` qemudev
2024-05-12 5:47 ` qemudev
2024-05-12 6:01 ` checkpatch
2024-05-12 7:03 ` |FAILURE| " 0-day Robot
2024-05-13 10:56 ` |SUCCESS| " dpdklab
2024-05-13 11:23 ` dpdklab
2024-05-13 11:27 ` dpdklab
2024-05-13 11:27 ` dpdklab
2024-05-13 11:28 ` dpdklab
2024-05-13 11:29 ` dpdklab
2024-05-13 11:29 ` dpdklab
2024-05-13 11:30 ` dpdklab
2024-05-13 11:30 ` |WARNING| " dpdklab
2024-05-13 11:30 ` |SUCCESS| " dpdklab
2024-05-13 11:31 ` dpdklab
2024-05-13 11:31 ` dpdklab
2024-05-13 11:33 ` dpdklab
2024-05-13 11:33 ` dpdklab
2024-05-13 11:33 ` dpdklab
2024-05-13 11:34 ` dpdklab
2024-05-13 11:34 ` dpdklab
2024-05-13 11:34 ` dpdklab
2024-05-13 11:35 ` dpdklab
2024-05-13 11:36 ` dpdklab
2024-05-13 11:36 ` dpdklab
2024-05-13 11:37 ` dpdklab
2024-05-13 11:37 ` dpdklab
2024-05-13 11:38 ` dpdklab
2024-05-13 11:38 ` dpdklab
2024-05-13 11:42 ` |WARNING| " dpdklab
2024-05-13 11:42 ` dpdklab
2024-05-13 11:43 ` dpdklab
2024-05-13 11:43 ` dpdklab
2024-05-13 11:43 ` |SUCCESS| " dpdklab
2024-05-13 11:43 ` dpdklab
2024-05-13 11:43 ` dpdklab
2024-05-13 11:44 ` dpdklab
2024-05-13 11:44 ` dpdklab
2024-05-13 11:44 ` |WARNING| " dpdklab
2024-05-13 11:44 ` |SUCCESS| " dpdklab
2024-05-13 11:45 ` dpdklab
2024-05-13 11:50 ` dpdklab
2024-05-13 11:51 ` dpdklab
2024-05-13 11:51 ` |WARNING| " dpdklab
2024-05-13 11:51 ` |SUCCESS| " dpdklab
2024-05-13 11:53 ` dpdklab
2024-05-13 11:53 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 11:54 ` dpdklab
2024-05-13 11:54 ` |WARNING| " dpdklab
2024-05-13 11:54 ` |SUCCESS| " dpdklab
2024-05-13 11:55 ` dpdklab
2024-05-13 11:55 ` dpdklab
2024-05-13 11:55 ` dpdklab
2024-05-13 11:55 ` |WARNING| " dpdklab
2024-05-13 11:57 ` |SUCCESS| " dpdklab
2024-05-13 11:57 ` dpdklab
2024-05-13 11:57 ` dpdklab
2024-05-13 11:58 ` dpdklab
2024-05-13 12:00 ` dpdklab
2024-05-13 12:00 ` dpdklab
2024-05-13 12:01 ` dpdklab [this message]
2024-05-13 12:01 ` |WARNING| " dpdklab
2024-05-13 12:01 ` |SUCCESS| " dpdklab
2024-05-13 12:02 ` dpdklab
2024-05-13 12:02 ` dpdklab
2024-05-13 12:02 ` dpdklab
2024-05-13 12:02 ` |WARNING| " dpdklab
2024-05-13 12:03 ` |SUCCESS| " dpdklab
2024-05-13 12:12 ` dpdklab
2024-05-13 12:13 ` dpdklab
2024-05-13 12:20 ` |WARNING| " dpdklab
2024-05-13 12:24 ` |SUCCESS| " dpdklab
2024-05-13 12:24 ` dpdklab
2024-05-13 12:25 ` dpdklab
2024-05-13 12:26 ` dpdklab
2024-05-13 12:26 ` dpdklab
2024-05-13 12:26 ` dpdklab
2024-05-13 12:27 ` dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:28 ` dpdklab
2024-05-13 12:29 ` dpdklab
2024-05-13 12:30 ` dpdklab
2024-05-13 12:32 ` dpdklab
2024-05-13 12:33 ` dpdklab
2024-05-13 12:46 ` dpdklab
2024-05-13 12:46 ` dpdklab
2024-05-13 12:59 ` dpdklab
2024-05-13 13:00 ` dpdklab
2024-05-13 13:08 ` dpdklab
2024-05-13 13:23 ` dpdklab
2024-05-13 13:56 ` 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=6642010d.050a0220.fa3fc.c6c5SMTPIN_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).