[GitHub] [druid] capistrant commented on issue #9324: Fix failing Calcite unit tests with existing work-a-round for calcite property setup

[GitBox <gi...@apache.org>]

capistrant commented on issue #9324: Fix failing Calcite unit tests with existing work-a-round for calcite property setup
URL: https://github.com/apache/druid/pull/9324#issuecomment-583039832
 
 
   @suneet-s what if you just run `mvn test` on the whole sql module? Your tests aren't actually failing for me but tests later on are. It is like calcite is setting up properties once and if the tests run in a certain order on a certain system, everything gets out of whack. But, that may work just fine on your environment... as in the issue referenced above, Gian seemed to have never seen it while the 2 others involved in the issue communications did see it. So dependent on underlying environment of developer executing tests I guess.
   
   I did some analysis on master over lunch that seemed to have narrowed it down to `CalcitePlannerModuleTest`:
   
   ##PASS
   * `mvn -Dtest=<test>` with each of the new test classes from #9279
   * `mvn -Dtest=DruidCalciteSchemaModuleTest,CalciteQueryTest test`
   * `mvn -Dtest=NamedDruidSchemaTest,CalciteQueryTest test`
   * `mvn -Dtest=NamedLookupSchemaTest,CalciteQueryTest test`
   * `mvn -Dtest=NamedSystemSchemaTest,CalciteQueryTest test` 
   ##FAIL
   * `mvn test`
   * `mvn -Dtest=CalcitePlannerModuleTest,CalciteQueryTest test`

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org