Travis integration

Status
Not open for further replies.
crowning

crowning

Well-known member
I've just created a pull-request for Bitcoin (I know, I know...but I couldn't resist
whistling1.gif
) and like the way the changes are immediately tested/build over at https://travis-ci.org/.

I'd like to have this for Dash as well...and it's free. Thoughts?
eduffield , flare ? Shall I do it?

Clipboard01.jpg



Details:
Clipboard02.jpg
 
flare said:
I have at least enabled Travis building --> https://travis-ci.org/dashpay/dash

But we need to have a look at some failing tests :)
Click to expand...

Thanks.

I guess ".travis.yml" needs some love. If I'd find some time next weekend I'll have a look.

Edit: yep, log says the tests are run which fail for Dash of course. The individual builds overwrite RUN_TESTS=false. Should be an easy fix. I'll do it later today.
 
Last edited by a moderator:
crowning said:
Thanks.

I guess ".travis.yml" needs some love. If I'd find some time next weekend I'll have a look.

Edit: yep, log says the tests are run which fail for Dash of course. The individual builds overwrite RUN_TESTS=false. Should be an easy fix. I'll do it later today.
Click to expand...
Disabling the tests is not a fix though :)
 
Almost there:

Clipboard01.jpg


I'll have another look later (or tomorrow) for the one failing build and create pull-requests once it's ready to merge.
 
flare said:
Good stuff, but please keep in mind: disabling the tests is not a solution to the problem :)

We are already running testless builds on https://dashpay.atlassian.net/builds/allPlans.action
Click to expand...

I know, but a first step must be to be able to replicate what Atlassian does, but automatically for each commit.

Fixing the tests for Dash is a different task, I think I had once start to fix some just to learn that it's not trivial to get all tests running.

BTW, Travis is not always reliable, I just re-run my repository-build and some builds failed (couldn't wget qrencode-3.4.3.tar.bz2, another build couldn't wget the Mac SDK, ...). Worked before without any problems...
 
crowning said:
I know, but a first step must be to be able to replicate what Atlassian does, but automatically for each commit.

Fixing the tests for Dash is a different task, I think I had once start to fix some just to learn that it's not trivial to get all tests running.

BTW, Travis is not always reliable, I just re-run my repository-build and some builds failed (couldn't wget qrencode-3.4.3.tar.bz2, another build couldn't wget the Mac SDK, ...). Worked before without any problems...
Click to expand...
I have found the root cause for the wget problems: wget on precise (which we are using on Travis) is outdated and not able to connect to SSLv3 enabled sites.

I have worked around this by using curl (see https://github.com/travis-ci/travis-ci/issues/5156)

So at least the testless ARM and MacOSX builds are green now, and I have made good progress on the failing tests for the other platforms - only 245 failing tests to go :)

upload_2016-1-27_14-44-23.png


We are getting there :)

upload_2016-1-27_15-4-52.png
 
flare said:
I have found the root cause for the wget problems: wget on precise (which we are using on Travis) is outdated and not able to connect to SSLv3 enabled sites.

I have worked around this by using curl (see https://github.com/travis-ci/travis-ci/issues/5156)

So at least the testless ARM and MacOSX builds are green now, and I have made good progress on the failing tests for the other platforms - only 245 failing tests to go :)
Click to expand...

Very good
icon_thumbsup.gif
:smile:

I'll merge/add this to my own Travis-branch and see what else is needed.
 
Code: 
if [ -n "$OSX_SDK" -a -f depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz ]; then tar -C depends/SDKs -xf depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz; fi

tar: This does not look like a tar archive

I can't access https://dash.org/depends-sources/sdks, so I don't know what's in there.
 
crowning said:
Code: 
if [ -n "$OSX_SDK" -a -f depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz ]; then tar -C depends/SDKs -xf depends/sdk-sources/MacOSX${OSX_SDK}.sdk.tar.gz; fi

tar: This does not look like a tar archive

I can't access https://dash.org/depends-sources/sdks, so I don't know what's in there.
Click to expand...
The path structure did not change, so https://dash.org/depends-sources/sdks/MacOSX10.7.sdk.tar.gz works

edit:

Down to 234 failures :)

x1Ehcjv.png


https://travis-ci.org/dashpay/dash/jobs/105368611#L4806
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top