DESCRIPTION

tmf: Add timeouts to potentially hanging tests

Change-Id: Ia429dad124844abbac44afa644250238c8a60f5a
Signed-off-by: Braxton Mccarthy xxx@xxx.xxx


COMMENTS

author: Brenden Conley
date: 2013-11-25 23:36:13.000000000

Patch Set 1: Verified-1

Build Failed 

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

-------------------------------------
author: Brenden Conley
date: 2013-11-26 06:54:51.000000000

Patch Set 1: -Verified

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

-------------------------------------
author: Brenden Conley
date: 2013-11-26 07:34:56.000000000

Patch Set 1: Verified+1

Build Successful 

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

-------------------------------------
author: Ricky Reeves
date: 2013-11-26 13:25:07.000000000

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

The timeout values look reasonable. For the scheduler, the longest test in my environment takes ~25 seconds. So, 60 seconds time should be fine.

-------------------------------------
author: Jordon Obrien
date: 2013-11-26 18:36:28.000000000

Patch Set 1: Code-Review+1

lgtm

-------------------------------------
author: Braxton Mccarthy
date: 2013-11-26 19:08:08.000000000

Patch Set 1:

Yeah I think giving 2x the normal expected time is safe, to take in consideration very old/slow hardware  (like the Hudson VMs ;)), but to actually fail if there is an issue and point out where it is.

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