[SPARK-47470][SQL][TESTS] Ignore IntentionallyFaultyConnectionProvider error in CliSuite
#45597
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to make
CliSuiteignoreIntentionallyFaultyConnectionProvidererror.Why are the changes needed?
Sometime,
hive-thriftserverCliSuiteworks correctly but failed due to the following because it matchesError:pattern.spark/sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/CliSuite.scala
Line 89 in bc378f4
IntentionallyFaultyConnectionProvideris a test resource fromsqlmodule which is not used inCliSuite.spark/sql/core/src/test/resources/META-INF/services/org.apache.spark.sql.jdbc.JdbcConnectionProvider
Line 18 in bc378f4
Does this PR introduce any user-facing change?
No, this is a test-only fix.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.