diff options
| author | David Gow <[email protected]> | 2020-06-16 06:47:30 +0000 |
|---|---|---|
| committer | Shuah Khan <[email protected]> | 2020-06-26 20:29:31 +0000 |
| commit | ee61492ab92b108b7db66acfd2c5f794244466b9 (patch) | |
| tree | 53f6c1f08236a85f5fb8f5e3e519a79859dfc250 /tools/perf/scripts/python/flamegraph.py | |
| parent | kunit: show error if kunit results are not present (diff) | |
| download | kernel-ee61492ab92b108b7db66acfd2c5f794244466b9.tar.gz kernel-ee61492ab92b108b7db66acfd2c5f794244466b9.zip | |
kunit: kunit_tool: Fix invalid result when build fails
When separating out different phases of running tests[1]
(build/exec/parse/etc), the format of the KunitResult tuple changed
(adding an elapsed_time variable). This is not populated during a build
failure, causing kunit.py to crash.
This fixes [1] to probably populate the result variable, causing a
failing build to be reported properly.
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=45ba7a893ad89114e773b3dc32f6431354c465d6
Signed-off-by: David Gow <[email protected]>
Reviewed-by: Brendan Higgins <[email protected]>
Tested-by: Brendan Higgins <[email protected]>
Signed-off-by: Shuah Khan <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions