automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: David Liu <dliu@iol.unh.edu>
Subject: [dpdk-test-report] |WARNING| pw78762 [PATCH] EEPROM Dump Feature
Date: Thu, 24 Sep 2020 18:46:36 +0200 (CEST)	[thread overview]
Message-ID: <20200924164636.1ED501DEDF@dpdk.org> (raw)
In-Reply-To: <20200924164453.50360-1-dliu@iol.unh.edu>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/78762

_coding style issues_


ERROR:TRAILING_WHITESPACE: trailing whitespace
#144: FILE: test_plans/eeprom_dump_test_plan.rst:53:
+   $

WARNING:TYPO_SPELLING: 'comapre' may be misspelled - perhaps 'compare'?
#248: FILE: tests/TestSuite_eeprom_dump.py:59:
+        # comapre the two files

ERROR:TRAILING_WHITESPACE: trailing whitespace
#249: FILE: tests/TestSuite_eeprom_dump.py:60:
+        result = self.dut.send_expect(f"diff testpmd_{testname}_{port}.txt ethtool_{testname}_{port}.txt", "#") $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#270: FILE: tests/TestSuite_eeprom_dump.py:81:
+            pmdout = self.dut.send_expect(f"show port {port} {testname}", "testpmd>") $

WARNING:TYPO_SPELLING: 'outout' may be misspelled - perhaps 'output'?
#273: FILE: tests/TestSuite_eeprom_dump.py:84:
+            # get length from testpmd outout

ERROR:TRAILING_WHITESPACE: trailing whitespace
#303: FILE: tests/TestSuite_eeprom_dump.py:114:
+            $

ERROR:TRAILING_WHITESPACE: trailing whitespace
#311: FILE: tests/TestSuite_eeprom_dump.py:122:
+        $

total: 5 errors, 2 warnings, 231 lines checked

       reply	other threads:[~2020-09-24 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200924164453.50360-1-dliu@iol.unh.edu>
2020-09-24 16:46 ` checkpatch [this message]
2020-09-24 18:55 ` [dpdk-test-report] |SUCCESS| pw78762 " 0-day Robot

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=20200924164636.1ED501DEDF@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=dliu@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).