On Tue, Oct 24, 2017 at 10:20 PM, William Roberts <bill.c.roberts@xxxxxxxxx> wrote: > On Oct 24, 2017 13:05, "Stephen Smalley" <sds@xxxxxxxxxxxxx> wrote: > > On Tue, 2017-10-24 at 09:26 -0700, William Roberts wrote: >> Error 52, which if it lines up with what I am reading is >> CURLE_GOT_NOTHING >> https://curl.haxx.se/libcurl/c/libcurl-errors.html >> >> That url/command combo seems valid, likely a transient issue with >> github. > > I restarted the job, and it failed again in the same way (but on > different cases). Then I restarted it a third time, and this time it > ran to completion. This seems problematic; we likely need to > reconsider any use of curl from the travis.yml file. > > > Weird. I wget things from sourceforge all the time. The only time I have > issues is when sourceforge is down. > >> On Tue, Oct 24, 2017 at 9:05 AM, Stephen Smalley <sds@xxxxxxxxxxxxx> >> wrote: [[...]] >> > Our .travis.yml seems to yield unstable results, >> > https://travis-ci.org/SELinuxProject/selinux/jobs/292128434 >> > >> > Don't know if it would help to instead download a refpolicy release >> > and >> > extract it, or if this is just transient. >> > It looks like transient networking issues between Travis-CI and Github. A possible fix would consists in using the Ubuntu package which provides refpolicy files: selinux-policy-dev. This however introduces the drawback that the package pulls in Ubuntu's version of checkpolicy, policycoreutils, libsepol... which may introduce incorrect test success if they happen to be used instead of the programs from the tested build. So I am not convinced by this. I am wondering whether using curl's --retry option would help to work around the networking issues which occurred. I am testing this in my "curl-retry" branch on Github [1] and will submit a patch if you think this may work. Nicolas [1] https://github.com/fishilico/selinux/commits/curl-retry
