DESCRIPTION

tmf: add way to not refresh project when adding a trace to experiment

Change-Id: I9b9a049bb196efe073d41986da0ee5211fc371d4
Signed-off-by: Ricky Reeves <Meredith xxx@xxx.xxx


COMMENTS

author: Ricky Reeves
date: 2014-07-18 17:39:09.000000000

Uploaded patch set 1.

-------------------------------------
author: Brenden Conley
date: 2014-07-18 20:33:58.000000000

Patch Set 1:

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7825/

-------------------------------------
author: Brenden Conley
date: 2014-07-18 20:57:09.000000000

Patch Set 1: Verified-1

Build Failed 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7825/ : FAILURE

-------------------------------------
author: Brenden Conley
date: 2014-07-19 14:47:35.000000000

Patch Set 1: -Verified

Build Started https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7845/

-------------------------------------
author: Brenden Conley
date: 2014-07-19 15:23:31.000000000

Patch Set 1: Verified+1

Build Successful 

https://hudson.eclipse.org/linuxtools/job/linuxtools-gerrit/7845/ : SUCCESS

-------------------------------------
author: Ivy Mitchell
date: 2014-07-21 16:45:25.000000000

Patch Set 1: Code-Review+1

This looks good to me. But I would like a test case if possible covering the "not refresh" branch.

-------------------------------------
author: Ricky Reeves
date: 2014-07-21 19:51:12.000000000

Patch Set 1: Verified+1 Code-Review+2

I agree that we need to add some test cases. We need to add this when having a new test implementation sprint.

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