DESCRIPTION

Bug 460863 - NPE in StatusHandlerRegistry when unit tests complete

Change-Id: I546a981a587eba3349c647db3f321497c21cfdab
Signed-off-by: Jayvion Booth xxx@xxx.xxx


COMMENTS

author: Jayvion Booth
date: 2016-08-18 14:46:36.000000000

Uploaded patch set 1.

-------------------------------------
author: Brenden Conley
date: 2016-08-18 14:46:42.000000000

Patch Set 1:

Build Started https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/10130/

-------------------------------------
author: Brenden Conley
date: 2016-08-18 15:10:45.000000000

Patch Set 1: Code-Review-1

Build Unstable 

https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/10130/ : UNSTABLE

-------------------------------------
author: Brenden Conley
date: 2016-08-18 15:16:00.000000000

Patch Set 1: -Code-Review

Build Started https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/10132/

-------------------------------------
author: Brenden Conley
date: 2016-08-18 15:39:34.000000000

Patch Set 1: Code-Review-1

Build Unstable 

https://hudson.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/10132/ : UNSTABLE

-------------------------------------
author: Camren Mckenzie
date: 2016-08-18 16:18:49.000000000

Patch Set 1: Code-Review-1

But that adds a new cost to everything at start up.

Surely the initialization should be guarded by a !isShuttingDown() guard?

-------------------------------------
author: Sebastian Porter
date: 2016-08-18 16:44:10.000000000

Patch Set 1: Code-Review-2

> But that adds a new cost to everything at start up.
 > 
 > Surely the initialization should be guarded by a !isShuttingDown()
 > guard?

+1.

-------------------------------------
author: Gerrit Code Review
date: 2016-08-24 11:31:08.000000000

Change has been successfully merged into the git repository by Sebastian Porter

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