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 2019/09/13 19:43:00 UTC
[jira] [Commented] (IMPALA-8944) Update and re-enable S3PlannerTest
[ https://issues.apache.org/jira/browse/IMPALA-8944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929482#comment-16929482 ]
Sahil Takiar commented on IMPALA-8944:
--------------------------------------
Looks like there was an attempt to only run fe tests beginning with {{S3*}} the target filesystem is S3 - https://github.com/apache/impala/blob/master/bin/run-all-tests.sh#L198 - however it looks like the logic is broken by https://github.com/apache/impala/blob/master/bin/run-all-tests.sh#L205 - the second filter cancels the first out out, which is why this doesn't work.
> Update and re-enable S3PlannerTest
> ----------------------------------
>
> Key: IMPALA-8944
> URL: https://issues.apache.org/jira/browse/IMPALA-8944
> Project: IMPALA
> Issue Type: Test
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
>
> It looks like we don't run {{S3PlannerTest}} in our regular Jenkins jobs. When run against a HDFS mini-cluster, they are skipped because the {{TARGET_FILESYSTEM}} is not S3. On our S3 jobs, they don't run either because we skip all fe/ tests (most of them don't work against S3 / assume they are running on HDFS).
> A few things need to be fixed to get this working:
> * The test cases in {{S3PlannerTest}} need to be fixed
> * The Jenkins jobs that runs the S3 tests needs the ability to run specific fe/ tests (e.g. just the {{S3PlannerTest}} and to skip the rest)
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org