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 "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/06/15 23:39:00 UTC
[jira] [Updated] (IMPALA-6249) Expose CMAKE_BUILD_TYPE via web UI
for build type detection
[ https://issues.apache.org/jira/browse/IMPALA-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong updated IMPALA-6249:
----------------------------------
Priority: Minor (was: Major)
> Expose CMAKE_BUILD_TYPE via web UI for build type detection
> -----------------------------------------------------------
>
> Key: IMPALA-6249
> URL: https://issues.apache.org/jira/browse/IMPALA-6249
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Tim Armstrong
> Priority: Minor
>
> IMPALA-6241 added a .cmake_build_type file with the CMAKE_BUILD_TYPE value for the last build. The file is used to detect the type of the build that the python tests are running against. However, this assumes that the tests are running from the same directory that the Impala cluster under test was built from, which isn't necessarily true for all dev workflows and for remote cluster tests.
> It would be convenient if CMAKE_BUILD_TYPE was exposed from the Impalad web UI. Currently we expose DEBUG/RELEASE depending on the value of NDEBUG - see GetVersionString() and impalad-host:25000/?json=true, but we could expose the precise build type, then allow the python tests to parse it from the web UI.
--
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