You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2021/01/27 04:14:27 UTC

[GitHub] [druid] suneet-s commented on a change in pull request #10791: Run integration tests in a second stage

suneet-s commented on a change in pull request #10791:
URL: https://github.com/apache/druid/pull/10791#discussion_r565016164



##########
File path: .travis.yml
##########
@@ -46,6 +45,7 @@ install: MAVEN_OPTS='-Xmx3000m' travis_wait 15 ${MVN} clean install -q -ff ${MAV
 stages:
   - name: test  # jobs that do not specify a stage get this default value
     if: type != cron
+  - name: it

Review comment:
       I like your suggestions. Trying to find the right balance and the right name for the stages is tough.
   
   I could move all the jdk 11 tests into the second stage, but then I can't think of what the name should be. I thought about slow / fast. But right now `intelliJ inspections` and the `indexing modules tests` take ~ 40 minutes, which is actually longer than most integration tests 😅 
   
   I think this split is good enough as a starting point, but would be extra happy if someone else proposed a more optimal split.




----------------------------------------------------------------
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



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