DESCRIPTION

CBD-477: post litmus results to dashboard datastore

- limit for access phase for now

Change-Id: Ided677622d80cc217e0de8af75813bc30d0d0a9a


COMMENTS

author: Hugo Blankenship
date: 2012-10-13 02:02:50.174000000

Patch Set 1:

Build Started http://qa.hq.northscale.net/job/testrunner-Jasmin Rangel-master/3453/ 

-------------------------------------
author: Hugo Blankenship
date: 2012-10-13 02:24:29.790000000

Patch Set 1:

Build Failed 

http://qa.hq.northscale.net/job/testrunner-Jasmin Rangel-master/3453/ : FAILURE

-------------------------------------
author: Nora Conway
date: 2012-10-15 17:10:26.246000000

Patch Set 1: Looks good to me, approved



-------------------------------------
author: Nora Conway
date: 2012-10-15 17:10:57.740000000

Patch Set 1:

might be better one day to have this posting decision be conf-file driven rather than hardcoded to "litmus" string equality

-------------------------------------
author: Alex Mcmahon
date: 2012-10-15 17:17:35.638000000

Patch Set 1: I would prefer that you didn't submit this

(1 inline comment)



Line:23, pytests/performance/eperf.py -> Do we really need full featured Couchbase client in order to do that?

Can litmus dashboard expose REST API for posting stats?

-------------------------------------
author: Daniel Blair
date: 2012-10-15 21:21:45.236000000

Patch Set 1: (1 inline comment)



Line:23, pytests/performance/eperf.py -> That's a good idea, let's tNathalie Landry about during our priority15 meeting.  It keeps testrunner cleaner, while it adds another layer of dependencies and one more point of failure.

-------------------------------------
author: Daniel Blair
date: 2012-10-22 23:48:55.856000000

Patch Set 1: Abandoned

replaced by http://review.couchbase.org/#/c/21861/

-------------------------------------
