| Age | Commit message (Collapse) | Author |
|---|
|
am: c4f7765019
Change-Id: I66948bfa9cd31b6537d3f9a9090e93c5a0d0ce50
|
|
am: a55a504a4b
Change-Id: Icd1460304fc06d40ffdf8478461047009bb4351f
|
|
am: 8c0608b2d5
Change-Id: I8d63825b7895fc69180706a8379917c626b94b9d
|
|
Exempt-From-Owner-Approval: meta data
BUG:69316045
Change-Id: Ie99e227de6c3132d3d682976f4b2ab47db1ff026
|
|
eb9f1bd727 am: e492846b4f
am: ecec17c6ed
Change-Id: I165cc2000f45f56d110bfc76c049c9939fc99fdc
|
|
am: e492846b4f
Change-Id: I08c5bfedc13baeba286f44375d54f83b2ca990ec
|
|
am: eb9f1bd727
Change-Id: I2452ce4de14b975327031685e530d467d1812f5a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pandas 0.19 requires Cython but it is not automatically installed by
Pip. So do it manually.
|
|
README: fix link to Thermal notebook
|
|
Signed-off-by: Michele Di Giorgio <michele.digiorgio@arm.com>
|
|
|
|
sched: SchedAssert: add getLastCpu()
|
|
Similar to getFirstCpu(), it's sometimes useful to know which CPU run
a given PID for the last time in the trace.
|
|
sched: SchedMultiAssert: add getCPUBusyTime
|
|
For multiple tasks, it's valuable to verify that they have ran on a set
of cpus for a given time. With SchedMultiAssert.getCPUBusyTime() we can
do that now!
|
|
The type of the level parameter for getResidency(), assertResidency()
and assertSwitch() is not displayed in the HTML documentation.
trappy.stats.Topology expects a string, so report that as the type.
|
|
|
|
|
|
get_pids_for_process() fixes
|
|
bart: set the version using an explicit file
|
|
process
We can't use .startswith() to match processes since sometimes a process
name is a substring of another process name. For example, in a trace
with processes "wmig" (pid 3268) and "wmig1" (pid 3269), if we use
.startswith("wmig"), the second process matches which is wrong. In this
trace, the only pid for the wmig process is 3268.
|
|
contain sched_switch events
|
|
There is no pythonic way of specifying the version of a project, [0]
describes 7 (seven!) ways of doing it. We were currently using method
5, setting the value in setup.py and using pkg_resources to get it from
the installed version. This works ok if you have installed the package
using python setup.py or pip, but fails if you are importing bart from a
checkout, which is what lisa do. Even worse, if you import it from lisa
but have an old bart version installed, bart.__version__ will tell you
the version of the installed bart, not the one you have imported and are
using.
Switch to use a version.py file that's distributed with the
project (method 3), as trappy did in ARM-software/trappy@712e6f93b308 .
Fixes #57
[0] https://packaging.python.org/en/latest/single_source_version/
|
|
Whoa! This is cool!
|
|
It's cool to point out which version is currently available in pypi.
Report it next to the travis badge.
|
|
README: explicitly state that the instructions are for Ubuntu 14.04 LTS
|
|
We have always implicitly supported Ubuntu 14.04 LTS as the minimum version.
State it explicitly in the README.
|
|
Add a link to the documentation to the readme file
|
|
We don't advertise enough the documentation. Add a link in the README
to raise awareness.
|
|
|
|
README.md: improve structure of README file
|
|
Travis CI support for continuosly running nosetests
|
|
|
|
|
|
|
|
|
|
sched: SchedAssert: fix documentation for getResidency()
|
|
The example of the getResidency() function is incomplete. Fix the
example so that it matches the documentation.
|
|
bart: use trappy.FTrace instead of trappy.Run
|
|
The signal tests all use dataframes for their tests that are manually
added to the trace object. trappy has a new API to do that. You can
create your trace as a BareTrace and then call add_parsed_event() to add
dataframes to it.
|
|
trappy now has a BareTrace class of which FTrace is one instance of. As
all that bart needs is the interface that BareTrace provides, let bart
check that the provided trace is an instance of it.
|
|
As of c26a32321053 ("ftrace: rename Run to FTrace"), trappy deprecated
trappy.Run in favour of trappy.FTrace. Move bart to use the new interface.
|
|
assert when the parsed statement returns a dataframe of bools
|
|
Sometimes it's useful to assert things like: "event:column == 3". Teach
assertStatement() handle the case where the result of parsing a
statement is a dataframe of bools.
|
