automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(113203) sid(23675) job(DTS_AUTO_1229) tests/unit_tests: fix self.__name__ error
Date: 21 Jun 2022 21:11:55 -0700	[thread overview]
Message-ID: <7f4525$j64871@fmsmga008-auth.fm.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

Test-Label: Intel-dts-pylama-test
Test-Status: FAILURE
http://dpdk.org/patch/113203
Subject: tests/unit_tests: fix self.__name__ error

_Testing issues_

Diff:
	tests/TestSuite_unit_tests_timer.py
	tests/TestSuite_unit_tests_ringpmd.py
	tests/TestSuite_unit_tests_ring.py
	tests/TestSuite_unit_tests_qos.py
	tests/TestSuite_unit_tests_power.py
	tests/TestSuite_unit_tests_pmd_perf.py
	tests/TestSuite_unit_tests_mempool.py
	tests/TestSuite_unit_tests_mbuf.py
	tests/TestSuite_unit_tests_lpm.py
	tests/TestSuite_unit_tests_loopback.py
	tests/TestSuite_unit_tests_kni.py
	tests/TestSuite_unit_tests_event_timer.py
	tests/TestSuite_unit_tests_eal.py
	tests/TestSuite_unit_tests_dump.py
	tests/TestSuite_unit_tests_cryptodev_func.py
	tests/TestSuite_unit_tests_crc.py
	tests/TestSuite_unit_tests_cmdline.py

DPDK:
	commit 9aa95b6fc4d0f166f8364f60c476f52dfcbe1082
	Author: David Marchand <david.marchand@redhat.com>
	Date:   Mon Jun 13 09:37:00 2022 +0200
	Comment: test: drop reference to removed tests

DTS:
	commit 9786172a52682db33fa0bf599622c838d992aa7d
	Author: Weiyuan li <weiyuanx.li@intel.com>
	Date:   Tue Jun 21 13:58:12 2022 +0800
	Comment: conf/test_case_checklist: add vlan_tx_restore not support

PYLAMA test failed information:
tests/TestSuite_unit_tests_mbuf.py:35: [E] E1101 Instance of 'TestUnitTestsMbuf' has no '__name__' member [pylint]
DPDK STV team

                 reply	other threads:[~2022-06-22  4:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='7f4525$j64871@fmsmga008-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --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).