wa: Rename results_processors to output_processors

For clarity and to better reflect their purpose, rename
`results_processors` to `output_processors`.

wa/framework/configuration/core.py

@@ -558,7 +558,7 @@ class MetaConfiguration(Configuration):
         'wa.framework.getters',
         'wa.framework.target.descriptor',
         'wa.instrumentation',
-        'wa.processors',
+        'wa.output_processors',
         'wa.workloads',
     ]
 
@@ -793,7 +793,7 @@ class RunConfiguration(Configuration):
             '''
         ),
         ConfigurationPoint(
-            'result_processors',
+            'output_processors',
             kind=toggle_set,
             default=['csv', 'status'],
             description='''
@@ -891,14 +891,14 @@ class JobSpec(Configuration):
                            Similar to IDs but do not have the uniqueness restriction.
                            If specified, labels will be used by some result
                            processes instead of (or in addition to) the workload
-                           name. For example, the csv result processor will put
+                           name. For example, the csv output processor will put
                            the label in the "workload" column of the CSV file.
                            '''),
         ConfigurationPoint('augmentations', kind=toggle_set, merge=True,
                            aliases=["instruments", "processors", "instrumentation",
-                                    "result_processors", "augment"],
+                                    "output_processors", "augment", "result_processor"],
                            description='''
-                           The instruments and result processors to enable (or
+                           The instruments and output processors to enable (or
                            disabled using a ~) during this workload spec. This combines the
                            "instrumentation" and "result_processors" from
                            previous versions of WA (the old entries are now
@@ -1073,7 +1073,7 @@ class JobGenerator(object):
                     msg = "'enabled_instruments' cannot be updated after it has been accessed"
                     raise RuntimeError(msg)
                 self._enabled_instruments.add(entry)
-            elif entry_cls.kind == 'result_processor':
+            elif entry_cls.kind == 'output_processor':
                 if self._read_enabled_processors:
                     msg = "'enabled_processors' cannot be updated after it has been accessed"
                     raise RuntimeError(msg)

wa/framework/configuration/execution.py

@@ -98,9 +98,9 @@ class ConfigManager(object):
         processors = []
         for name in self.enabled_processors:
             try:
-                proc = self.plugin_cache.get_plugin(name, kind='result_processor')
+                proc = self.plugin_cache.get_plugin(name, kind='output_processor')
             except NotFoundError:
-                msg = 'Result processor "{}" not found'
+                msg = 'Output Processor "{}" not found'
                 raise NotFoundError(msg.format(name))
             processors.append(proc)
         return processors

wa/framework/configuration/parsers.py

@@ -208,9 +208,9 @@ def _load_file(filepath, error_name):
 
 def merge_augmentations(raw):
     """
-    Since, from configuration perspective, result processors and instrumens are
+    Since, from configuration perspective, output processors and instrumens are
     handled identically, the configuration entries are now interchangeable. E.g. it is
-    now valid to specify a result processor in instrumentation list. This is to make things
+    now valid to specify a output processor in instrumentation list. This is to make things
     eassier for the users, as, from their perspective, the distinction is somewhat arbitrary.
 
     For backwards compatibility, both entries are still valid, and this