From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jie Zhou <jizh@linux.microsoft.com>
Subject: |WARNING| pw106541 [PATCH v15 09/11] app/test: skip tests that are not supported yet
Date: Wed, 26 Jan 2022 06:12:34 +0100 (CET) [thread overview]
Message-ID: <20220126051234.78E9F120715@dpdk.org> (raw)
In-Reply-To: <1643173844-27341-10-git-send-email-jizh@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/106541
_coding style issues_
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#1105: FILE: app/test/test_func_reentrancy.c:492:
+ if (RTE_EXEC_ENV_IS_WINDOWS)
+ return TEST_SKIPPED;
WARNING:TABSTOP: Statements should start on a tabstop
#1106: FILE: app/test/test_func_reentrancy.c:493:
+ return TEST_SKIPPED;
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#1212: FILE: app/test/test_hash_perf.c:727:
+ if (RTE_EXEC_ENV_IS_WINDOWS)
+ return TEST_SKIPPED;
WARNING:TABSTOP: Statements should start on a tabstop
#1213: FILE: app/test/test_hash_perf.c:728:
+ return TEST_SKIPPED;
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#1552: FILE: app/test/test_lcores.c:387:
+ if (RTE_EXEC_ENV_IS_WINDOWS)
+ return TEST_SKIPPED;
WARNING:TABSTOP: Statements should start on a tabstop
#1553: FILE: app/test/test_lcores.c:388:
+ return TEST_SKIPPED;
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#2056: FILE: app/test/test_rcu_qsbr_perf.c:617:
+ if (RTE_EXEC_ENV_IS_WINDOWS)
+ return TEST_SKIPPED;
WARNING:TABSTOP: Statements should start on a tabstop
#2057: FILE: app/test/test_rcu_qsbr_perf.c:618:
+ return TEST_SKIPPED;
total: 0 errors, 8 warnings, 1965 lines checked
parent reply other threads:[~2022-01-26 5:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1643173844-27341-10-git-send-email-jizh@linux.microsoft.com>]
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=20220126051234.78E9F120715@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jizh@linux.microsoft.com \
--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).