[
https://issues.apache.org/jira/browse/IMPALA-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Knupp resolved IMPALA-7399.
---------------------------------
Resolution: Fixed
> Add a script for generating junit XML type output for arbitrary build steps
> ---------------------------------------------------------------------------
>
> Key: IMPALA-7399
> URL: https://issues.apache.org/jira/browse/IMPALA-7399
> Project: IMPALA
> Issue Type: New Feature
> Components: Infrastructure
> Affects Versions: Not Applicable
> Reporter: David Knupp
> Priority: Major
>
> Junit XML has become a defacto standard for outputting automated test
> results. Jenkins consumes junit XML output to generate final test reports.
> This makes triaging failed builds much easier.
> While Impala's test frameworks already produce junit XML, it would be nice to
> take produce junit XML for earlier build steps that aren't formally tests,
> e.g., compilation and data loading. This will make it easier to diagnose
> these failures on jobs that run on jenkins.impala.io (as opposed to requiring
> users to read through raw console output.)
> This script is also being used as a starting point for setting up a formal
> internal python library for Impala development that can be installed via
> {{pip install -e <path to Impala/lib/python>}}. We expect other packages to
> be added to this library over time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
