"Pluggable" result processors

[GoogleCodeExporter]

One result processor might wish to post results to BRRD or to Sponge, and 
others might want to do god knows what.

One approach: do nothing, except spit out XML results to a filename 
specified on the command line. Other tools can subsequently read that.

Possibly-nicer approach: let result processor classes be set in caliperrc or 
wherever; then they could be passed real live Java objects instead of 
spending a lot of effort re-parsing XML.

I see us just doing the first approach for now, but I don't know long-term..
just filing this for future reference I guess.

Original issue reported on code.google.com by kevinb@google.com on 19 Jan 2010 at 5:32

[GoogleCodeExporter]

Another option - teach these other apps how to slurp our data from appengine. 
The 
only risk here is that our appengine app isn't secure.

Original comment by limpbizkit on 20 Jan 2010 at 3:59

[GoogleCodeExporter]

as a man who doesn't trust the cloud and doesn't believe in xml, i liked the 
idea of arbitrary implementations of 
some result-processor interface myself. would that simplify DalvikRunner's job 
at all?

Original comment by e...@google.com on 20 Jan 2010 at 4:15

[GoogleCodeExporter]

Original comment by kevinb@google.com on 7 Jun 2010 at 5:55

• Added labels: Milestone-Post-1.0

[GoogleCodeExporter]

Original comment by kevinb@google.com on 19 Mar 2011 at 3:06

• Added labels: Type-Enhancement

[GoogleCodeExporter]

already half-done.

Original comment by kevinb@google.com on 19 Sep 2011 at 6:41

• Added labels: Milestone-1.0
• Removed labels: Milestone-Post-1.0

[GoogleCodeExporter]

We already have the standard interface but we're hardcoding the list of 
implementations to iterate through.  This could be handled in caliperrc in a 
very similar way to how we handle pluggable instruments.  If it proves to be 
hard for some unknown reason then it may not be crucial but I think it should 
be easy.

Original comment by kevinb@google.com on 14 Nov 2011 at 8:47

[GoogleCodeExporter]

Original comment by kevinb@google.com on 16 Nov 2011 at 8:35

[GoogleCodeExporter]

Original comment by kevinb@google.com on 8 Feb 2012 at 9:49

• Added labels: Component-Runner

[GoogleCodeExporter]

We think those hardcoded resultprocessors should be enough and that to do other 
things you should just slurp results out of appengine, but may revisit this 
much later.

Original comment by kevinb@google.com on 21 Mar 2012 at 6:08

• Added labels: Milestone-Post-1.0
• Removed labels: Milestone-1.0

[GoogleCodeExporter]

Original comment by kevinb@google.com on 1 Nov 2012 at 8:32

[GoogleCodeExporter]

This actually just sort of happened.  Now, result processors can be added by 
adding entries to the config file that look like 
`results.someName.class=some.package.SomeResultProcessorImpl`

Original comment by gak@google.com on 11 Apr 2013 at 10:33

[GoogleCodeExporter]

Original comment by gak@google.com on 11 Apr 2013 at 10:33

• Changed state: Fixed