automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: jasvinder.singh@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [PatchWork]|ERROR| pw12547 ip_pipeline: add script file for pipeline to core mappings
Date: 10 May 2016 23:02:25 -0700	[thread overview]
Message-ID: <acb6cf$t3uou3@fmsmga002.fm.intel.com> (raw)

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


Test-Label: Intel Niantic on Fedora
Test-Status: ERROR

Patchwork ID: 12547
http://www.dpdk.org/dev/patchwork/patch/12547/
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Fri,  6 May 2016 20:04:24 +0100
DPDK git baseline: 84c9b5a9fe926f1aa033dc5352be8d4a5e0b789d

Check patch error:
12547: 
ERROR: trailing whitespace
#92: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:35:
+# This script maps the set of pipelines identified (MASTER pipelines 
+are $

ERROR: trailing whitespace
#93: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:36:
+# ignored) from the input configuration file to the set of cores $

ERROR: trailing whitespace
#94: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:37:
+# provided as input argument and creates configuration files for each 
+of $

ERROR: trailing whitespace
#119: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:62:
+#----------------------------------------------------------------------
+------- $

ERROR: trailing whitespace
#120: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:63:
+def popcount(mask):                                                                          $

ERROR: trailing whitespace
#123: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:66:
+#----------------------------------------------------------------------
+------- $

ERROR: trailing whitespace
#130: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:73:
+    $

ERROR: trailing whitespace
#133: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:76:
+#----------------------------------------------------------------------
+------- $

ERROR: trailing whitespace
#153: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:96:
+#----------------------------------------------------------------------
+--- $

ERROR: trailing whitespace
#158: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:101:
+#----------------------------------------------------------------------
+--- $

ERROR: trailing whitespace
#213: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:156:
+                    $

ERROR: trailing whitespace
#236: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:179:
+                $

ERROR: trailing whitespace
#242: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:185:
+            $

ERROR: trailing whitespace
#248: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:191:
+        $

ERROR: trailing whitespace
#258: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:201:
+                $

ERROR: trailing whitespace
#267: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:210:
+        #end while         $

ERROR: trailing whitespace
#268: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:211:
+    #end function    $

ERROR: trailing whitespace
#316: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:259:
+        $

ERROR: trailing whitespace
#329: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:272:
+            print('(%d,%d)' %(self.cores[cores_count].pipelines, $

ERROR: trailing whitespace
#346: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:289:
+        self.stage1_reset()  $

ERROR: trailing whitespace
#350: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:293:
+        $

ERROR: trailing whitespace
#380: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:323:
+            $

ERROR: trailing whitespace
#398: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:341:
+            $

ERROR: trailing whitespace
#420: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:363:
+            $

ERROR: trailing whitespace
#421: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:364:
+            $

ERROR: trailing whitespace
#443: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:386:
+            $

ERROR: trailing whitespace
#454: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:397:
+        #check if file traceing is enabled         $

ERROR: trailing whitespace
#463: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:406:
+    
+ #---------------------------------------------------------------------
+ --- $

ERROR: trailing whitespace
#485: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:428:
+    
+ #---------------------------------------------------------------------
+ --- $

ERROR: trailing whitespace
#489: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:432:
+        $

ERROR: trailing whitespace
#510: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:453:
+        # update the in_buf as per the arr_pipelines2cores      $

ERROR: trailing whitespace
#514: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:457:
+        $

ERROR: trailing whitespace
#515: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:458:
+        #by now the in_buf is all set to be written to file $

ERROR: trailing whitespace
#518: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:461:
+        $

ERROR: trailing whitespace
#519: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:462:
+        #write out the comments $

ERROR: trailing whitespace
#545: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:488:
+#----------------------------------------------------------------------
+------- $

ERROR: trailing whitespace
#582: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:525:
+            $

ERROR: trailing whitespace
#591: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:534:
+            $

ERROR: trailing whitespace
#599: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:542:
+        self.arr2_pipelines2cores.clear() $

ERROR: trailing whitespace
#637: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:580:
+        #end while $

ERROR: trailing whitespace
#672: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:615:
+        #check if file traceing is enabled         $

ERROR: trailing whitespace
#674: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:617:
+            return $

ERROR: trailing whitespace
#742: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:685:
+   $

ERROR: trailing whitespace
#747: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:690:
+            outFileName += 'HT'            $

ERROR: trailing whitespace
#754: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:697:
+        # update the in_buf as per the arr_pipelines2cores $

ERROR: trailing whitespace
#757: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:700:
+       $

ERROR: trailing whitespace
#758: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:701:
+        #by now the in_buf is all set to be written to file $

ERROR: trailing whitespace
#782: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:725:
+    #end function stage2_process_file $

ERROR: trailing whitespace
#791: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:734:
+        $

ERROR: trailing whitespace
#815: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:758:
+#----------------------------------------------------------------------
+------- $

ERROR: trailing whitespace
#820: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:763:
+        self.in_filename = os.path.basename(self.in_file_namepath) $

ERROR: trailing whitespace
#822: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:765:
+        $

ERROR: trailing whitespace
#831: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:774:
+        $

ERROR: trailing whitespace
#832: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:775:
+        self.max_cores = 15 $

ERROR: trailing whitespace
#840: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:783:
+        # save the num of cores input (or the truncated value) $

ERROR: trailing whitespace
#843: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:786:
+       $

ERROR: trailing whitespace
#847: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:790:
+        print("self.in_file_namepath = ", self.in_file_namepath) $

ERROR: trailing whitespace
#1007: FILE: examples/ip_pipeline/config/pipeline-to-core-mapping.py:950:
+# python trick - so that our Python files can act as either reusable 
+modules, $

total: 58 errors, 0 warnings, 990 lines checked

NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
      scripts/cleanfile

/home/patchWorkOrg/patches/dpdk-dev-v2-ip_pipeline-add-script-file-for-pipeline-to-core-mappings.patch has style problems, please review.

If any of these errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS.


Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
ICC:16.0.2
i686-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-clang: compile pass



DPDK STV team 


                 reply	other threads:[~2016-05-11  6:02 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='acb6cf$t3uou3@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=jasvinder.singh@intel.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).