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: |WARNING| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr
Date: Wed, 02 Apr 2025 20:16:15 -0700 (PDT)	[thread overview]
Message-ID: <67edfd7f.050a0220.1800bb.124cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250403023059.1762841-3-probb@iol.unh.edu>

Test-Label: iol-dts-check-format-testing
Test-Status: WARNING
http://dpdk.org/patch/152747

_Testing issues_

Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Thursday, April 03 2025 02:30:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7246d0a80cb79a04e1334393ef507aa4ef7accd9

152746-152747 --> testing issues

Upstream job id: DTS-Check-Format-Pipeline#38

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 in ./
----------------
Formatting code with ruff:
61 files left unchanged

Linting in ./
-------------
Found 1 error (1 fixed, 0 remaining).
dts/framework/config/test_run.py: needs update
The "needs update" files have been fixed by the linter.
Please update your commit.

Checking types in ./
--------------------
framework/config/test_run.py:306: error: Unsupported left operand type for + ("Iterable[TestSuiteConfig]")  [operator]
Found 1 error in 1 file (checked 61 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/32936/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-03  3:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250403023059.1762841-3-probb@iol.unh.edu>
2025-04-03  2:07 ` |SUCCESS| pw152746-152747 [PATCH 2/2] dts: update dpdk-devbind script regex qemudev
2025-04-03  2:12 ` qemudev
2025-04-03  2:36 ` |SUCCESS| pw152747 " checkpatch
2025-04-03  3:16 ` dpdklab [this message]
2025-04-03  3:41 ` |SUCCESS| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr dpdklab
2025-04-03  3:42 ` dpdklab
2025-04-03  3:42 ` |SUCCESS| pw152747 [PATCH 2/2] dts: update dpdk-devbind script regex 0-day Robot
2025-04-03  3:44 ` |SUCCESS| pw152746-152747 [PATCH] [2/2] dts: update dpdk-devbind scr dpdklab
2025-04-03  3:48 ` |FAILURE| " dpdklab
2025-04-03  3:57 ` dpdklab
2025-04-03  3:58 ` |PENDING| " dpdklab
2025-04-03  4:05 ` dpdklab
2025-04-03  4:07 ` dpdklab
2025-04-03  4:24 ` |SUCCESS| " dpdklab
2025-04-03  4:54 ` dpdklab
2025-04-03  5:09 ` dpdklab
2025-04-03  5:18 ` dpdklab
2025-04-03  5:19 ` dpdklab
2025-04-03  5:24 ` dpdklab
2025-04-03  5:33 ` dpdklab
2025-04-03  5:34 ` dpdklab
2025-04-03  8:56 ` dpdklab
2025-04-03 19:24 ` |FAILURE| " dpdklab
2025-04-03 21:43 ` |SUCCESS| " dpdklab
2025-04-03 22:07 ` |FAILURE| " dpdklab
2025-04-04 16:04 ` |SUCCESS| " 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=67edfd7f.050a0220.1800bb.124cSMTPIN_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).