From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw153135-153136 [PATCH] [2/2] dts: add port control testin
Date: Wed, 23 Apr 2025 19:08:08 -0700 (PDT) [thread overview]
Message-ID: <68099d08.050a0220.38c5e6.1327SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250424014412.3849896-3-probb@iol.unh.edu>
Test-Label: iol-dts-check-format-testing
Test-Status: WARNING
http://dpdk.org/patch/153136
_Testing issues_
Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Thursday, April 24 2025 01:44:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:327efc58fe5dd1702a0c1e1b81b8172bc5152c00
153135-153136 --> testing issues
Upstream job id: DTS-Check-Format-Pipeline#42
Test environment and result as below:
+--------------------+------------------+
| Environment | dts-check-format |
+====================+==================+
| Ubuntu 22.04.5 LTS | FAIL |
+--------------------+------------------+
==== 20 line log output for Ubuntu 22.04.5 LTS (dts-check-format): ====
Formatting code with ruff:
1 file reformatted, 61 files left unchanged
dts/tests/TestSuite_port_control.py: needs update
The "needs update" files have been reformatted.
Please update your commit.
Linting in ./
-------------
All checks passed!
dts/tests/TestSuite_port_control.py: needs update
The "needs update" files have been fixed by the linter.
Please update your commit.
Checking types in ./
--------------------
Success: no issues found in 62 source files
Summary for ./
--------------
Found 2 errors
==== End log output ====
Ubuntu 22.04.5 LTS
Kernel: 5.15.0-119-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33059/
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:[~2025-04-24 2:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250424014412.3849896-3-probb@iol.unh.edu>
2025-04-24 1:21 ` |SUCCESS| pw153135-153136 [PATCH 2/2] dts: add port control testing suite qemudev
2025-04-24 1:25 ` qemudev
2025-04-24 1:49 ` |SUCCESS| pw153136 " checkpatch
2025-04-24 2:08 ` dpdklab [this message]
2025-04-24 2:13 ` |SUCCESS| pw153135-153136 [PATCH] [2/2] dts: add port control testin dpdklab
2025-04-24 2:18 ` |PENDING| " dpdklab
2025-04-24 2:20 ` |SUCCESS| " dpdklab
2025-04-24 2:31 ` |PENDING| " dpdklab
2025-04-24 2:33 ` |SUCCESS| " dpdklab
2025-04-24 2:34 ` dpdklab
2025-04-24 2:37 ` dpdklab
2025-04-24 2:37 ` |PENDING| " dpdklab
2025-04-24 2:40 ` |SUCCESS| " dpdklab
2025-04-24 2:42 ` |PENDING| " dpdklab
2025-04-24 2:44 ` |SUCCESS| " dpdklab
2025-04-24 2:50 ` dpdklab
2025-04-24 2:57 ` |PENDING| " dpdklab
2025-04-24 3:04 ` |SUCCESS| pw153136 [PATCH 2/2] dts: add port control testing suite 0-day Robot
2025-04-24 3:20 ` |SUCCESS| pw153135-153136 [PATCH] [2/2] dts: add port control testin dpdklab
2025-04-24 3:41 ` dpdklab
2025-04-24 3:41 ` dpdklab
2025-04-24 4:07 ` dpdklab
2025-04-24 4:13 ` dpdklab
2025-04-24 5:18 ` 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=68099d08.050a0220.38c5e6.1327SMTPIN_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).