alistair23-linux/tools/testing/kunit
David Gow ee61492ab9 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 <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Tested-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2020-06-26 14:29:31 -06:00
..
configs kunit: Run all KUnit tests through allyesconfig 2020-03-20 16:17:39 -06:00
test_data kunit: show error if kunit results are not present 2020-06-26 14:29:10 -06:00
.gitattributes kunit: kunit_parser: make parser more robust 2020-03-20 16:15:57 -06:00
.gitignore .gitignore: add SPDX License Identifier 2020-03-25 11:50:48 +01:00
kunit.py kunit: kunit_tool: Fix invalid result when build fails 2020-06-26 14:29:31 -06:00
kunit_config.py kunit: kunit_config: Fix parsing of CONFIG options with space 2020-06-26 14:27:35 -06:00
kunit_kernel.py kunit: add --make_options 2020-03-23 17:08:22 -06:00
kunit_parser.py kunit: show error if kunit results are not present 2020-06-26 14:29:10 -06:00
kunit_tool_test.py kunit: show error if kunit results are not present 2020-06-26 14:29:10 -06:00