You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/11 11:00:00 UTC

[jira] [Commented] (PHOENIX-6828) Test failure in master branch : LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny

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

ASF GitHub Bot commented on PHOENIX-6828:
-----------------------------------------

mnpoonia opened a new pull request, #1528:
URL: https://github.com/apache/phoenix/pull/1528

   This test is failing on indexscrutiny tool. I am assuming that index scrutiny tool is not modified after the new index design. For now we can use the index tool instead of index scrutiny as it has all the functionality that scrutiny tool has. File another JIRA to fix index scrutiny




> Test failure in master branch : LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny
> -----------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6828
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6828
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.2.0
>            Reporter: Rushabh Shah
>            Assignee: Aman Poonia
>            Priority: Major
>
> The following tests are failing in master branch
> [ERROR] Failures: 
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny:229 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny:229 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny:229 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny:229 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithIndex_runScrutiny:169 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithIndex_runScrutiny:169 expected:<2> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithIndex_runScrutiny:165 expected:<3> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithIndex_runScrutiny:165 expected:<3> but was:<1>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithViews_runScrutiny:353 expected:<2> but was:<0>
> [ERROR]   LogicalTableNameIT.testUpdatePhysicalTableNameWithViews_runScrutiny:353 expected:<2> but was:<0>
> Failed in 2 different PR builds and confirmed locally on master that it is failing.
> 1. https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1518/4/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt
> 2. https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1522/1/testReport/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)