You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/08/09 21:49:01 UTC

[jira] [Commented] (IMPALA-7399) Add a script for generating junit XML type output for arbitrary build steps

    [ https://issues.apache.org/jira/browse/IMPALA-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575440#comment-16575440 ] 

ASF subversion and git services commented on IMPALA-7399:
---------------------------------------------------------

Commit 8f9f91f38bebba3c69fc15cc522840941b871658 in impala's branch refs/heads/master from [~dknupp]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=8f9f91f ]

IMPALA-7399: Add script in lib/python to generate junit XML.

This patch adds a script to generate junit XML reports for arbitrary
build steps. It's also being used to seed the creation of an internal
python library for Impala development that can be pip installed into
a development environment.

Change-Id: If6024d74075ea69b8ee20d1fc3cc9c1ff821ba5b
Reviewed-on: http://gerrit.cloudera.org:8080/11128
Reviewed-by: David Knupp <dk...@cloudera.com>
Tested-by: David Knupp <dk...@cloudera.com>


> 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-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org