rteval.git, branch work/v2.0

Add some input data validation when parsing the output histogram from cyclictest

2014-01-22T19:01:26+00:00

Backport of commit e0ca74e9c9f7f83a9db08d062b5ca8bdf05ff748 from v1.3x

Signed-off-by: Clark Williams 
Signed-off-by: David Sommerseth

Fix MANIFEST.in - remove trailing / on the doc directory

2013-11-08T17:21:34+00:00

This caused Python 2.7 sdist to not include the files listed in
the recursive-include statement.

Signed-off-by: David Sommerseth

Fix formatting syntax, %d -> %s

2013-11-08T16:21:24+00:00

Signed-off-by: David Sommerseth

Fix --onlyload and reportdir being set to None

2013-11-08T16:19:46+00:00

Signed-off-by: David Sommerseth

cleaned up changelog section of specfile

2013-09-05T16:22:11+00:00

properly escaped any '%' characters used in changelog entries
and removed trailing whitespace.

Signed-off-by: Clark Williams

Added new measurement module, sysstat

2013-06-17T19:00:52+00:00

This module runs in parallel with cyclictest and will every minute
use sysstat/sadc to collect all available system statistics.  These
statistics is both added as a single file to the tarball and embedded
into the summary.xml.

Also changed the polling time which checks if measurement and load modules
are alive from every second to every minute.

Signed-off-by: David Sommerseth

cyclictest: Added trace-cmd extract when breaktrace aborts exection

2013-05-02T19:13:25+00:00

This adds a dependency of the trace-cmd package as well, but it will
improve the ability to better understand what happened when this the
threshold broke.

Signed-off-by: David Sommerseth

cyclictest: Don't bother reporting 'variance'

2013-04-15T14:57:51+00:00

The data used to do the mathematical reporting is based on histogram data,
where the calculated variance will be rather pointless to gather.

Imagine you have 3 samples in the historgram in the 2000µs slot, even if
you have quite a lot of data with the average measurements around 50µs,
the calculated "variance" for that time slot will be (1950^2)*3.  Even
though the final variance calculation will divide on number of samples
gathered, it will take an enormous amount of samples within a the lower
time slots to make this value interesting.

So rather, don't report or save the calculated variance. However, the
standard deviation is based on the variance, that value is far more sane
due to the needed square root function on the final variance value.  So
it gives a far more sane and interesting value.  The applied math in the
cyclictest module should be fine itself, it's just the variance value
that isn't much interesting on this kind of data source.

Signed-off-by: David Sommerseth

Don't report any buckets where no samples have been collected

2013-03-15T21:52:54+00:00

Signed-off-by: David Sommerseth

Added timestamps tracking when each module starts and stops

2013-03-14T20:35:04+00:00

Currently ignoring load modules in general, as the  tags
isn't easily extended.  Not convinced it makes any sense to
track these time stamps on load modules anyway.

Signed-off-by: David Sommerseth