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| pw154092 [PATCH] [1/1] dts: fix deterministic doc
Date: Fri, 06 Jun 2025 11:34:20 -0700 (PDT)	[thread overview]
Message-ID: <684334ac.250a0220.39f858.6954SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250606093502.31767-1-cfamullaconrad@suse.com>

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

_Testing issues_

Submitter: Clemens Famulla-Conrad <cfamullaconrad@suse.com>
Date: Friday, June 06 2025 09:35:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:dd5979ceb777801288fb3ca4caa565bc34a370d8

154092 --> testing issues

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

Test environment and result as below:

+--------------+------------------+
| Environment  | dts-check-format |
+==============+==================+
| Ubuntu 24.04 | FAIL             |
+--------------+------------------+

==== 20 line log output for Ubuntu 24.04 (dts-check-format): ====
Formatting in ./
----------------
Formatting code with ruff:
65 files left unchanged

Linting in ./
-------------
All checks passed!

Checking types in ./
--------------------
framework/testbed_model/traffic_generator/capturing_traffic_generator.py:75: error: Incompatible default for argument "capture_name" (default has type "None", argument has type "str")  [assignment]
framework/testbed_model/traffic_generator/capturing_traffic_generator.py:75: note: PEP 484 prohibits implicit Optional. Accordingly, mypy has changed its default to no_implicit_optional=True
framework/testbed_model/traffic_generator/capturing_traffic_generator.py:75: note: Use https://github.com/hauntsaninja/no_implicit_optional to automatically upgrade your codebase
Found 1 error in 1 file (checked 65 source files)

Summary for ./
--------------
Found 1 errors
==== End log output ====

Ubuntu 24.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-06 18:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250606093502.31767-1-cfamullaconrad@suse.com>
2025-06-06  9:14 ` |SUCCESS| pw154092 [PATCH 1/1] " qemudev
2025-06-06  9:18 ` qemudev
2025-06-06  9:37 ` checkpatch
2025-06-06 10:47 ` 0-day Robot
2025-06-06 18:34 ` dpdklab [this message]
2025-06-06 19:04 ` |SUCCESS| pw154092 [PATCH] [1/1] " dpdklab
2025-06-06 20:06 ` dpdklab
2025-06-06 20:25 ` dpdklab
2025-06-06 20:26 ` |PENDING| " dpdklab
2025-06-06 20:30 ` |SUCCESS| " dpdklab
2025-06-06 20:38 ` |PENDING| " dpdklab
2025-06-06 21:11 ` dpdklab
2025-06-06 21:46 ` |SUCCESS| " dpdklab
2025-06-06 22:36 ` |PENDING| " dpdklab
2025-06-06 23:00 ` |SUCCESS| " dpdklab
2025-06-06 23:01 ` dpdklab
2025-06-06 23:01 ` dpdklab
2025-06-06 23:02 ` dpdklab
2025-06-06 23:03 ` dpdklab
2025-06-06 23:05 ` dpdklab
2025-06-06 23:08 ` dpdklab
2025-06-06 23:22 ` |WARNING| " dpdklab
2025-06-06 23:35 ` |SUCCESS| " dpdklab
2025-06-07  0:04 ` dpdklab
2025-06-07  4: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=684334ac.250a0220.39f858.6954SMTPIN_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).