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 "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/10/09 16:20:00 UTC
[jira] [Resolved] (IMPALA-8304) Generate JUnitXML symptom for
compilation/CMake failures
[ https://issues.apache.org/jira/browse/IMPALA-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell resolved IMPALA-8304.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Generate JUnitXML symptom for compilation/CMake failures
> --------------------------------------------------------
>
> Key: IMPALA-8304
> URL: https://issues.apache.org/jira/browse/IMPALA-8304
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 3.3.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 4.0
>
>
> When compilation or another CMake command fails, it should generate JUnitXML containing the output of the command that failed to allow faster triage. All of the information is currently available in the Jenkins log, but due to the parallel nature of the build, the failure can be buried in logging. Some builds are extremely verbose (e.g. clang tidy) and can hide errors in megabytes of logs.
> This should apply to both frontend and backend compilation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org