You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/06/11 17:27:00 UTC
[jira] [Commented] (PHOENIX-5942) ParameterizedIndexUpgradeIT is
too slow
[ https://issues.apache.org/jira/browse/PHOENIX-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133503#comment-17133503 ]
Hudson commented on PHOENIX-5942:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #3954 (See [https://builds.apache.org/job/PreCommit-PHOENIX-Build/3954/])
PHOENIX-5942 - ParameterizedIndexUpgradeToolIT is too slow (#798) (gjacoby: rev 1080422e626c2451556dc4c3f66c6c0e1010693a)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/ParameterizedIndexUpgradeToolIT.java
> ParameterizedIndexUpgradeIT is too slow
> ---------------------------------------
>
> Key: PHOENIX-5942
> URL: https://issues.apache.org/jira/browse/PHOENIX-5942
> Project: Phoenix
> Issue Type: Bug
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Minor
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5942-4.x.v1.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The test creates the same tables and views for each test case, drops them between, and recreates them. In addition each test case is doing index upgrades / downgrades which requires disabling tables and rebuilding them. Plus there are a lot of test cases, because of the cross-product of the parameters.
> According to [~achouhan], this is causing some builds to fail with timeouts, and taking 20-30 min for me locally the last time I needed to add a test case. Looks like it's time to refactor this test so it goes faster.
> I suspect just having each test case create its own test-specific tables (so no more dropping) would help, but that may not be enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)