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 "Sahil Takiar (JIRA)" <ji...@apache.org> on 2018/11/01 15:45:00 UTC

[jira] [Commented] (IMPALA-6249) Expose several build flags via web UI

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

Sahil Takiar commented on IMPALA-6249:
--------------------------------------

[~dknupp] could you take a look at [https://gerrit.cloudera.org/#/c/11410/12/tests/run-tests.py] - the change is related to IMPALA-4417 which is assigned to you. To summarize the change, in addition to a whitelist for the {{tests/}} directories, we added a blacklist. This forces all folders under the {{tests/}} directory to choose whether they contain tests. This helps avoid scenario such as IMPALA-7691 where our Jenkins jobs don't run certain tests because we forget to add the folder to the whitelist. IMPALA-4417 is a good long term solution, but since it sounds like it requires quite a bit of work, we thought adding the blacklist would help until IMPALA-4417 is fixed.

> Expose several build flags via web UI
> -------------------------------------
>
>                 Key: IMPALA-6249
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6249
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Assignee: Sahil Takiar
>            Priority: Minor
>         Attachments: Screen Shot 2018-09-06 at 11.47.45 AM.png
>
>
> 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