sandynz opened a new issue, #20273:
URL: https://github.com/apache/shardingsphere/issues/20273

   ## Bug Report
   
   ### Which version of ShardingSphere did you use?
   master branch
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   both
   
   ### Expected behavior
   IT run passed
   
   ### Actual behavior
   Some integration test failed.
   e.g. 
https://github.com/apache/shardingsphere/runs/7891247703?check_suite_focus=true
   ```
   Error:  2022-08-18 03:07:44.071 [main] o.a.s.t.i.f.watcher.ITWatcher - Error 
case: assertExecute[proxy: encrypt -> PostgreSQL -> Literal -> SHOW DATABASE 
RESOURCES], message: java.lang.AssertionError: 
   Expected: is 
"{\"dataSourceProperties\":{},\"healthCheckProperties\":{},\"initializationFailTimeout\":1,\"validationTimeout\":5000,\"leakDetectionThreshold\":0,\"poolName\":\"HikariPool-1\",\"registerMbeans\":false,\"allowPoolSuspension\":false,\"autoCommit\":true,\"isolateInternalQueries\":false}"
        but: was 
"{\"dataSourceProperties\":{},\"healthCheckProperties\":{},\"initializationFailTimeout\":1,\"validationTimeout\":5000,\"leakDetectionThreshold\":0,\"poolName\":\"HikariPool-2\",\"registerMbeans\":false,\"allowPoolSuspension\":false,\"autoCommit\":true,\"isolateInternalQueries\":false}"
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
        at org.junit.Assert.assertThat(Assert.java:956)
        at org.junit.Assert.assertThat(Assert.java:923)
        at 
org.apache.shardingsphere.test.integration.engine.rql.BaseRQLIT.assertObjectValue(BaseRQLIT.java:85)
        at 
org.apache.shardingsphere.test.integration.engine.rql.BaseRQLIT.assertRow(BaseRQLIT.java:79)
        at 
org.apache.shardingsphere.test.integration.engine.rql.BaseRQLIT.assertRows(BaseRQLIT.java:69)
        at 
org.apache.shardingsphere.test.integration.engine.rql.BaseRQLIT.assertResultSet(BaseRQLIT.java:45)
        at 
org.apache.shardingsphere.test.integration.engine.rql.GeneralRQLIT.assertExecute(GeneralRQLIT.java:53)
   ```
   
   ### Reason analyze (If you can)
   The root cause might be #17883, `poolName` will be shown in `SHOW DATABASE 
RESOURCES;` result, but pool name is not customized in integration test 
configuration files.
   
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   ### Example codes for reproduce this issue (such as a github link).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to