*: fix an unstable test case TestJoinSystemTableContainsView

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #55414

Problem Summary:

What changed and how does it work?

In the past, the check is introduced to prevent bug when we change INFORMATION_SCHEMA reader.
It works by run the query twice, one with filters push down and the other without, comparing the result.

It's intend to prevent regressions during refactoring like #55156 #55253

But this check is not stable enough. When a query on INFORMATION_SCHEMA run twice, the result is not the same.
Too many false positive cases.
I have already skiped so many cases, but new cases continue coming ... so it's better to remove this check.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @tiancaiamao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tiancaiamao]

Skip this case.
@wjhuang2016 said if any new failed cases emerge, he will take over them.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.8562%. Comparing base (1b172b6) to head (d205bde).
Report is 6 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55431        +/-   ##
================================================
+ Coverage   73.0060%   74.8562%   +1.8502%     
================================================
  Files          1576       1578         +2     
  Lines        440772     440924       +152     
================================================
+ Hits         321790     330059      +8269     
+ Misses        99280      90595      -8685     
- Partials      19702      20270       +568     

Flag	Coverage Δ
integration	49.1349% <100.0000%> (?)
unit	71.9334% <100.0000%> (-0.1612%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5363% <ø> (+6.5224%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Defined2014, wjhuang2016

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Defined2014,wjhuang2016]
• pkg/infoschema/OWNERS [wjhuang2016]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-15 07:18:13.683119367 +0000 UTC m=+425178.386589011: ☑️ agreed by Defined2014.
• 2024-08-15 08:19:42.933684186 +0000 UTC m=+428867.637153822: ☑️ agreed by wjhuang2016.