Of course I just noticed when the `./gradlew install` is fast, is because the 
openwhisk/tools/travis/setup.sh script does ./gradlew :tests:compileTestScala, 
which is indeed much slower. 

I also noticed the gradle versions are different between main repo and 
runtime-docker, so will try out updating runtime-docker to same gradle 
version...

On 10/1/18, 4:45 PM, "Tyson Norris" <[email protected]> wrote:

    Hi –
    I’m troubleshooting a problem with this PR build [1] where a test fails due 
to a difference in exception handling between akka http client (now used in 
runtime test base class), and apache http client. This change was merged to OW 
master some time ago in [2].
    
    The problem I’m having is that the builds and test work great locally. The 
travis build is behaving as if the tests base classes (built by cloning 
incubator-openwhisk, and running `./gradlew install`) are not installed fresh 
each build, but I cannot see anywhere in travis config or build scripts where 
they might be cached. One reason I suspect cacheing (aside from the build 
failing) is that the elapsed time spent in `./gradlew install` is 15s in travis 
– this is way faster than I ever see running the same on a clean system locally.
    
    Any ideas?
    
    Thanks
    Tyson
    
    [1] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Fincubator-openwhisk-runtime-docker%2Fbuilds%2F435891993&amp;data=02%7C01%7Ctnorris%40adobe.com%7Cdc85e3274e6e46f2524408d627f7eeb2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740343143609349&amp;sdata=4%2FOZEvMg04O%2BfmGRvvv9QOM0qS4Np6uQDTO%2Fnxi7LSg%3D&amp;reserved=0
    [2] 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fincubator-openwhisk%2Fcommit%2F15bb04a449f621d262c2687a7b8417241f3856b8&amp;data=02%7C01%7Ctnorris%40adobe.com%7Cdc85e3274e6e46f2524408d627f7eeb2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636740343143609349&amp;sdata=dzr76uuIp0DYLF4e%2FpqYvMxUKg5L2lFNTFqzBBlDKyA%3D&amp;reserved=0
    
    

Reply via email to