New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce test time to avoid hitting Travis CI time limit #441

Merged
merged 2 commits into from Dec 14, 2016

Conversation

Projects
None yet
1 participant
@dexX7
Copy link
Member

dexX7 commented Dec 12, 2016

Our Travis CI runs are sometimes failing, because we hit the time limit.

This PR is an attempt to cut some time by lowering the Omni log level. We still have another test run with maximum logging. It also disables the Bitcoin Core RPC tests in one test run.

edit: hmm.. looks like it's still not enough.

@dexX7 dexX7 added the ci and tests label Dec 12, 2016

@dexX7 dexX7 added this to the Next release milestone Dec 12, 2016

@dexX7 dexX7 changed the title Don't use maximum logging for more than one Travis CI run Reduce test time to avoid hitting Travis CI time limit Dec 14, 2016

@dexX7 dexX7 force-pushed the dexX7:0.2-ci-minimum-logging branch from 4b22238 to 39850eb Dec 14, 2016

@dexX7 dexX7 merged commit 39850eb into OmniLayer:develop Dec 14, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

dexX7 added a commit that referenced this pull request Dec 14, 2016

Merge #441: Reduce test time to avoid hitting Travis CI time limit
39850eb Don't run Bitcoin Core RPC tests in Linux x64 test run (dexX7)
f71f1a9 Don't use maximum logging for more than one Travis CI run (dexX7)
@dexX7

This comment has been minimized.

Copy link
Member

dexX7 commented Dec 14, 2016

@zathras-crypto: so this PR should cut some time, and while testing, it was enough in one run, but wasn't enough in another run.

Then I contacted the Travis CI support and asked, if they may increase our allowed build time to 60 minutes to rebuild the caches, so we don't need to rebuild all dependencies every time, and they agreed. However, this is only temporary.

Given this, we hopefully have fully populated caches in a few minutes, and the PR should reduce the time for testing even further.

Let's hope it's enough in the future. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment