clintropolis commented on pull request #11283:
URL: https://github.com/apache/druid/pull/11283#issuecomment-846329402


   This script appears to be working correctly so far on the 3 example PRs that 
are linked to this one.
   
   The java only change ran most of the test suites, but skipped the 
web-console, web-console e2e, and docs tests, 
https://travis-ci.com/github/apache/druid/builds/226501655
   https://travis-ci.com/github/apache/druid/jobs/506826045#L667
   
   The web-console correctly test skipped all jobs except web-console and 
web-console e2e tests, 
https://travis-ci.com/github/apache/druid/builds/226501846 cutting total CI 
compute time down from over 24 hours to  under 2.5 hrs (~30 minutes of wall 
time)
   
   The 3rd PR contains a first commit that is only a doc change, where all 
tests were skipped except for the docs test 
https://travis-ci.com/github/apache/druid/builds/226501778, using ~2 hr of 
compute time, but then a second commit was added to a java file which has 
triggered all of the java tests to run in addition to the docs tests (to ensure 
that the diff from all of the PR commits is what we see due to how travis runs 
PR builds, instead of just the last commit as the git command our script is 
using might suggest, see 
https://travis-ci.com/github/apache/druid/jobs/507046243#L662 which has the 
files from both commits).
   
   The branch build ran the entire test suite and skipped nothing, 
https://travis-ci.com/github/apache/druid/builds/226501106, though looking at 
the log I guess I could stand to change the script a bit to print that the 
reason for not skipping the tests is because it is not a PR build to make 
clearer the reason the tests are being run.
   
   I also added a unit test for this test skipping script, "script checks", 
https://travis-ci.com/github/apache/druid/jobs/506826488, since it was already 
getting a bit complicated and will only continue to do so as we add more 
functionality to this script to more selectively run the java tests.


-- 
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to