You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2018/05/30 23:47:00 UTC
[jira] [Assigned] (KUDU-2460) parse_test_failure.py doesn't handle
errors outside of test cases
[ https://issues.apache.org/jira/browse/KUDU-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adar Dembo reassigned KUDU-2460:
--------------------------------
Assignee: Todd Lipcon
Todd has been working on a patch to fix these and other issues in parse_test_failure.py.
> parse_test_failure.py doesn't handle errors outside of test cases
> -----------------------------------------------------------------
>
> Key: KUDU-2460
> URL: https://issues.apache.org/jira/browse/KUDU-2460
> Project: Kudu
> Issue Type: Bug
> Components: test
> Affects Versions: 1.7.0
> Reporter: Adar Dembo
> Assignee: Todd Lipcon
> Priority: Major
>
> The parse_test_failure.py script generates JUnit-style XML report files for tests that either failed to generate one themselves, or whose generated XML file is missing critical information. For example, gtest's XML report generation logic isn't aware of TSAN warnings, so a test with a TSAN warning ends up with a clean XML report, even though the report ought to show that some test failed with a TSAN warning.
> Unfortunately, parse_test_failure.py silently drops e.g. TSAN warnings that were reported _outside_ of a particular test run. This can lead to missing test failures in test dashboards and the like.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)