Get CI working
ChrisRackauckas opened this issue · comments
High on the priority list is to get CI working. I am not sure how, but we should check what the other FEniCS.jl had to do to make it work.
Noted. I will look at how travis is generally set to work, and look at adapting it to our problem. I'll probably try and do this throughout the downtime at JuliaCon if possible.
…________________________________
From: Christopher Rackauckas <notifications@github.com>
Sent: 18 June 2017 15:53:15
To: JuliaDiffEq/FEniCS.jl
Cc: Subscribed
Subject: [JuliaDiffEq/FEniCS.jl] Get CI working (#9)
High on the priority list is to get CI working. I am not sure how, but we should check what the other FEniCS.jl had to do to make it work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#9>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APV6MaVlg0ZR9qNsFYYLGqPkUu2mHDaGks5sFTnbgaJpZM4N9hC_>.
I'll take a look at this right now and see what I can do.
https://travis-ci.org/JuliaDiffEq/FEniCS.jl/jobs/244237546#L236
Travis has my problem...
Looks like it could be a Python2 vs Python3 problem? FEniCS is Python 3 ?
Regarding CI, AppVeyor is mainly (only?) for windows if I'm not mistaken. Should we remove it completely?
Yes. Add to the README that we won't even hope for Windows to work anytime soon and just move on.
@ChrisRackauckas has setup Continuous Integration.