[PHOENIX-6828] Test failure in master branch : LogicalTableNameIT.testUpdatePhysicalIndexTableName_runScrutiny

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 5.2.0
• Assignee: Aman Poonia
• Reporter: Rushabh Shah
• Created: 01/Nov/22 17:01
• Updated: 22/Nov/22 13:21
• Resolved: 22/Nov/22 10:08

Description

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/

Issue Links

• is caused by: PHOENIX-6776 Abort scans of closed connections at ScanningResultIterator
• links to: GitHub Pull Request #1528