analysis: Add additional assertion to troubleshoot test failure
authorMarc-Andre Laperle <marc-andre.laperle@ericsson.com>
Tue, 1 Nov 2016 13:23:12 +0000 (09:23 -0400)
committerMarc-André Laperle <marc-andre.laperle@ericsson.com>
Thu, 3 Nov 2016 17:49:14 +0000 (13:49 -0400)
commit516a0f0f213544918ace0b0b80b224c215abf95d
tree2cef19e68cea6fbc03b017b96ebad2fe6b728bff
parente2b65c8f7737b1f9c7e1ae8ef212365c3be3da25
analysis: Add additional assertion to troubleshoot test failure

The axis range in the tested SWTChart doesn't have the correct range.
It would be interesting to know if the window range of the trace is
correct.

Change-Id: I001787016a5b3d78b83b526175d8a1e9656e2790
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/84277
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Tested-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
Reviewed-by: Hudson CI
analysis/org.eclipse.tracecompass.analysis.os.linux.ui.swtbot.tests/src/org/eclipse/tracecompass/analysis/os/linux/ui/swtbot/tests/latency/SystemCallLatencyScatterChartViewTest.java
This page took 0.02405 seconds and 5 git commands to generate.