lttng: Fix intermittent MemoryUsageViewTest failure
authorMarc-Andre Laperle <marc-andre.laperle@ericsson.com>
Mon, 14 Mar 2016 01:16:11 +0000 (21:16 -0400)
committerMarc-Andre Laperle <marc-andre.laperle@ericsson.com>
Mon, 14 Mar 2016 15:32:47 +0000 (11:32 -0400)
commit6206fd7500118cd99d6e0a449bab8de87646bd89
treeabc21d6feec5630edecf0c9143c7d15e2e4143dc
parenta86dc130985da0500cd61d8d8614e76d09a1ef31
lttng: Fix intermittent MemoryUsageViewTest failure

It is possible that a thread gets added to the memory usage chart
before the process name is determined. Once the process name is
determined, a new series is added to the chart but the old one is not
deleted. Not only this fails the test because the chart contains too
many series, but it shows the wrong information to the user.

To reproduce the issue, you can add a Thread.sleep(5000) in
UstMemoryStateProvider around line 222, before the process name gets
added to the state system.

Change-Id: I95631758e0fdffbc094a3adb923b7019841a4a60
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/68312
Reviewed-by: Hudson CI
Reviewed-by: Bernd Hufmann <bernd.hufmann@ericsson.com>
Tested-by: Bernd Hufmann <bernd.hufmann@ericsson.com>
lttng/org.eclipse.tracecompass.lttng2.ust.ui/src/org/eclipse/tracecompass/internal/lttng2/ust/ui/views/memusage/MemoryUsageViewer.java
This page took 0.02604 seconds and 5 git commands to generate.