travis: several tries to download cunit

Message ID 20170127192150.9730-1-maxim.uvarov@linaro.org
State New
Headers show

Commit Message

Maxim Uvarov Jan. 27, 2017, 7:21 p.m.
some time curl fails to download cunit from sf.net or it's
mirrors. Try 10 times with 1 second delay.

Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

---
 .travis.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.11.0.295.gd7dffce

Comments

Bill Fischofer Jan. 29, 2017, 10:03 p.m. | #1
On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:
> some time curl fails to download cunit from sf.net or it's

> mirrors. Try 10 times with 1 second delay.

>

> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

> ---

>  .travis.yml | 2 +-

>  1 file changed, 1 insertion(+), 1 deletion(-)

>

> diff --git a/.travis.yml b/.travis.yml

> index 03e61b18..363c1b3f 100644

> --- a/.travis.yml

> +++ b/.travis.yml

> @@ -25,7 +25,7 @@ before_install:

>

>  #       Install cunit for the validation tests because distro version is too old and fails C99 compile

>          - export CUNIT_VERSION=2.1-3

> -        - curl -sSOL http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> +        - for _ in {1..10}; do http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2 && break; sleep 1; done


If we're going to make this more robust, what happens if the 10
attempts all fail? Do we just run off the rails as before or make an
attempt to quit with some sort of useful debug msg?

>          - tar -jxf *.bz2

>          - cd CUnit*

>          - ./bootstrap

> --

> 2.11.0.295.gd7dffce

>
Mike Holmes Jan. 30, 2017, 2:30 p.m. | #2
Currently we have forked the repo and we pull from that copy, that copy is
on Anders poeple.linaro.org for the internal Jenkins CI

Maybe we add cunit fork to the lng offical repo location so that we can do
this from github also and not  have to point at a personal location ?

Mike

On 29 January 2017 at 17:03, Bill Fischofer <bill.fischofer@linaro.org>
wrote:

> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org>

> wrote:

> > some time curl fails to download cunit from sf.net or it's

> > mirrors. Try 10 times with 1 second delay.

> >

> > Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

> > ---

> >  .travis.yml | 2 +-

> >  1 file changed, 1 insertion(+), 1 deletion(-)

> >

> > diff --git a/.travis.yml b/.travis.yml

> > index 03e61b18..363c1b3f 100644

> > --- a/.travis.yml

> > +++ b/.travis.yml

> > @@ -25,7 +25,7 @@ before_install:

> >

> >  #       Install cunit for the validation tests because distro version

> is too old and fails C99 compile

> >          - export CUNIT_VERSION=2.1-3

> > -        - curl -sSOL http://sourceforge.net/

> projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> > +        - for _ in {1..10}; do http://souirceforge.net/

> projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> && break; sleep 1; done

>

> If we're going to make this more robust, what happens if the 10

> attempts all fail? Do we just run off the rails as before or make an

> attempt to quit with some sort of useful debug msg?

>

> >          - tar -jxf *.bz2

> >          - cd CUnit*

> >          - ./bootstrap

> > --

> > 2.11.0.295.gd7dffce

> >

>




-- 
Mike Holmes
Program Manager - Linaro Networking Group
Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
"Work should be fun and collaborative, the rest follows"
Bill Fischofer Jan. 30, 2017, 2:38 p.m. | #3
On Mon, Jan 30, 2017 at 8:30 AM, Mike Holmes <mike.holmes@linaro.org> wrote:
> Currently we have forked the repo and we pull from that copy, that copy is

> on Anders poeple.linaro.org for the internal Jenkins CI

>

> Maybe we add cunit fork to the lng offical repo location so that we can do

> this from github also and not  have to point at a personal location ?


If we're going to fork, agree we should do so "officially" rather than
in a personal repo.

>

> Mike

>

> On 29 January 2017 at 17:03, Bill Fischofer <bill.fischofer@linaro.org>

> wrote:

>>

>> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org>

>> wrote:

>> > some time curl fails to download cunit from sf.net or it's

>> > mirrors. Try 10 times with 1 second delay.

>> >

>> > Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

>> > ---

>> >  .travis.yml | 2 +-

>> >  1 file changed, 1 insertion(+), 1 deletion(-)

>> >

>> > diff --git a/.travis.yml b/.travis.yml

>> > index 03e61b18..363c1b3f 100644

>> > --- a/.travis.yml

>> > +++ b/.travis.yml

>> > @@ -25,7 +25,7 @@ before_install:

>> >

>> >  #       Install cunit for the validation tests because distro version

>> > is too old and fails C99 compile

>> >          - export CUNIT_VERSION=2.1-3

>> > -        - curl -sSOL

>> > http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>> > +        - for _ in {1..10}; do

>> > http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>> > && break; sleep 1; done

>>

>> If we're going to make this more robust, what happens if the 10

>> attempts all fail? Do we just run off the rails as before or make an

>> attempt to quit with some sort of useful debug msg?

>>

>> >          - tar -jxf *.bz2

>> >          - cd CUnit*

>> >          - ./bootstrap

>> > --

>> > 2.11.0.295.gd7dffce

>> >

>

>

>

>

> --

> Mike Holmes

> Program Manager - Linaro Networking Group

> Linaro.org │ Open source software for ARM SoCs

> "Work should be fun and collaborative, the rest follows"

>

>
Maxim Uvarov Jan. 30, 2017, 2:45 p.m. | #4
On 01/30/17 01:03, Bill Fischofer wrote:
> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:

>> some time curl fails to download cunit from sf.net or it's

>> mirrors. Try 10 times with 1 second delay.

>>

>> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

>> ---

>>  .travis.yml | 2 +-

>>  1 file changed, 1 insertion(+), 1 deletion(-)

>>

>> diff --git a/.travis.yml b/.travis.yml

>> index 03e61b18..363c1b3f 100644

>> --- a/.travis.yml

>> +++ b/.travis.yml

>> @@ -25,7 +25,7 @@ before_install:

>>

>>  #       Install cunit for the validation tests because distro version is too old and fails C99 compile

>>          - export CUNIT_VERSION=2.1-3

>> -        - curl -sSOL http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>> +        - for _ in {1..10}; do http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2 && break; sleep 1; done

> 

> If we're going to make this more robust, what happens if the 10

> attempts all fail? Do we just run off the rails as before or make an

> attempt to quit with some sort of useful debug msg?

> 


In that case CI will fail. It is clear from the log that it failed due
to missing CUnit.

Actually that is strange why it happens. I see the OE also downloads it
from sourceforge:
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-devtools/cunit/cunit_2.1-3.bb?h=master
and as back up there is mirror, which is also source forge:
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf?h=blinky

But there is no any reason to have mirror because curl has option to
follow redirections on the mirrors. I think that something in mirror
switching algorithm might be wrong. If I'm understand right main site
redirects to mirror which on access is down. Curl just fails with empty
response. On next try mirror list has to be already updated and alive
mirror will be selected.

Log message should be like this:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/196256512/log.txt


If that later will not help we can put CUnit sources to our github.

Maxim.



>>          - tar -jxf *.bz2

>>          - cd CUnit*

>>          - ./bootstrap

>> --

>> 2.11.0.295.gd7dffce

>>
Maxim Uvarov Jan. 30, 2017, 2:47 p.m. | #5
On 01/30/17 17:38, Bill Fischofer wrote:
> On Mon, Jan 30, 2017 at 8:30 AM, Mike Holmes <mike.holmes@linaro.org> wrote:

>> Currently we have forked the repo and we pull from that copy, that copy is

>> on Anders poeple.linaro.org for the internal Jenkins CI

>>

>> Maybe we add cunit fork to the lng offical repo location so that we can do

>> this from github also and not  have to point at a personal location ?

> 

> If we're going to fork, agree we should do so "officially" rather than

> in a personal repo.

> 


CUnit is in svn, so it will not be clean fork. We can put tar.gz to some
repo. But for now I would increase number of tries.

Maxim.


>>

>> Mike

>>

>> On 29 January 2017 at 17:03, Bill Fischofer <bill.fischofer@linaro.org>

>> wrote:

>>>

>>> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org>

>>> wrote:

>>>> some time curl fails to download cunit from sf.net or it's

>>>> mirrors. Try 10 times with 1 second delay.

>>>>

>>>> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

>>>> ---

>>>>  .travis.yml | 2 +-

>>>>  1 file changed, 1 insertion(+), 1 deletion(-)

>>>>

>>>> diff --git a/.travis.yml b/.travis.yml

>>>> index 03e61b18..363c1b3f 100644

>>>> --- a/.travis.yml

>>>> +++ b/.travis.yml

>>>> @@ -25,7 +25,7 @@ before_install:

>>>>

>>>>  #       Install cunit for the validation tests because distro version

>>>> is too old and fails C99 compile

>>>>          - export CUNIT_VERSION=2.1-3

>>>> -        - curl -sSOL

>>>> http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>>>> +        - for _ in {1..10}; do

>>>> http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>>>> && break; sleep 1; done

>>>

>>> If we're going to make this more robust, what happens if the 10

>>> attempts all fail? Do we just run off the rails as before or make an

>>> attempt to quit with some sort of useful debug msg?

>>>

>>>>          - tar -jxf *.bz2

>>>>          - cd CUnit*

>>>>          - ./bootstrap

>>>> --

>>>> 2.11.0.295.gd7dffce

>>>>

>>

>>

>>

>>

>> --

>> Mike Holmes

>> Program Manager - Linaro Networking Group

>> Linaro.org │ Open source software for ARM SoCs

>> "Work should be fun and collaborative, the rest follows"

>>

>>
Mike Holmes Jan. 30, 2017, 2:57 p.m. | #6
On 30 January 2017 at 09:47, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:

> On 01/30/17 17:38, Bill Fischofer wrote:

> > On Mon, Jan 30, 2017 at 8:30 AM, Mike Holmes <mike.holmes@linaro.org>

> wrote:

> >> Currently we have forked the repo and we pull from that copy, that copy

> is

> >> on Anders poeple.linaro.org for the internal Jenkins CI

> >>

> >> Maybe we add cunit fork to the lng offical repo location so that we can

> do

> >> this from github also and not  have to point at a personal location ?

> >

> > If we're going to fork, agree we should do so "officially" rather than

> > in a personal repo.

> >

>

> CUnit is in svn, so it will not be clean fork. We can put tar.gz to some

> repo. But for now I would increase number of tries.

>


It is so easy to push the tar and then there is never an issue, I think
that would be better for internal CI so I will check with Anders and try to
move that at least.


>

> Maxim.

>

>

> >>

> >> Mike

> >>

> >> On 29 January 2017 at 17:03, Bill Fischofer <bill.fischofer@linaro.org>

> >> wrote:

> >>>

> >>> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov <maxim.uvarov@linaro.org

> >

> >>> wrote:

> >>>> some time curl fails to download cunit from sf.net or it's

> >>>> mirrors. Try 10 times with 1 second delay.

> >>>>

> >>>> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>

> >>>> ---

> >>>>  .travis.yml | 2 +-

> >>>>  1 file changed, 1 insertion(+), 1 deletion(-)

> >>>>

> >>>> diff --git a/.travis.yml b/.travis.yml

> >>>> index 03e61b18..363c1b3f 100644

> >>>> --- a/.travis.yml

> >>>> +++ b/.travis.yml

> >>>> @@ -25,7 +25,7 @@ before_install:

> >>>>

> >>>>  #       Install cunit for the validation tests because distro version

> >>>> is too old and fails C99 compile

> >>>>          - export CUNIT_VERSION=2.1-3

> >>>> -        - curl -sSOL

> >>>> http://sourceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> >>>> +        - for _ in {1..10}; do

> >>>> http://souirceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> >>>> && break; sleep 1; done

> >>>

> >>> If we're going to make this more robust, what happens if the 10

> >>> attempts all fail? Do we just run off the rails as before or make an

> >>> attempt to quit with some sort of useful debug msg?

> >>>

> >>>>          - tar -jxf *.bz2

> >>>>          - cd CUnit*

> >>>>          - ./bootstrap

> >>>> --

> >>>> 2.11.0.295.gd7dffce

> >>>>

> >>

> >>

> >>

> >>

> >> --

> >> Mike Holmes

> >> Program Manager - Linaro Networking Group

> >> Linaro.org │ Open source software for ARM SoCs

> >> "Work should be fun and collaborative, the rest follows"

> >>

> >>

>

>



-- 
Mike Holmes
Program Manager - Linaro Networking Group
Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
"Work should be fun and collaborative, the rest follows"
Maxim Uvarov Jan. 30, 2017, 3:11 p.m. | #7
On 01/30/17 17:57, Mike Holmes wrote:
> 

> 

> On 30 January 2017 at 09:47, Maxim Uvarov <maxim.uvarov@linaro.org

> <mailto:maxim.uvarov@linaro.org>> wrote:

> 

>     On 01/30/17 17:38, Bill Fischofer wrote:

>     > On Mon, Jan 30, 2017 at 8:30 AM, Mike Holmes <mike.holmes@linaro.org <mailto:mike.holmes@linaro.org>> wrote:

>     >> Currently we have forked the repo and we pull from that copy, that copy is

>     >> on Anders poeple.linaro.org <http://poeple.linaro.org> for the internal Jenkins CI

>     >>

>     >> Maybe we add cunit fork to the lng offical repo location so that we can do

>     >> this from github also and not  have to point at a personal location ?

>     >

>     > If we're going to fork, agree we should do so "officially" rather than

>     > in a personal repo.

>     >

> 

>     CUnit is in svn, so it will not be clean fork. We can put tar.gz to some

>     repo. But for now I would increase number of tries.

> 

> 

> It is so easy to push the tar and then there is never an issue, I think

> that would be better for internal CI so I will check with Anders and try

> to move that at least.

>  


we also need account 2 things:

a) we should do exactly what is said in our README.
b) we should use official repo. If it's dead other people also can not
build odp. If we mirror it we should update README.

If we said that we support:

apt-get install libcunit1-dev

then maybe get rid text from DEPENDANCIES about building it from src?
People should know where to get it if they build it from src.

Maxim.


> 

> 

>     Maxim.

> 

> 

>     >>

>     >> Mike

>     >>

>     >> On 29 January 2017 at 17:03, Bill Fischofer

>     <bill.fischofer@linaro.org <mailto:bill.fischofer@linaro.org>>

>     >> wrote:

>     >>>

>     >>> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov

>     <maxim.uvarov@linaro.org <mailto:maxim.uvarov@linaro.org>>

>     >>> wrote:

>     >>>> some time curl fails to download cunit from sf.net

>     <http://sf.net> or it's

>     >>>> mirrors. Try 10 times with 1 second delay.

>     >>>>

>     >>>> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org

>     <mailto:maxim.uvarov@linaro.org>>

>     >>>> ---

>     >>>>  .travis.yml | 2 +-

>     >>>>  1 file changed, 1 insertion(+), 1 deletion(-)

>     >>>>

>     >>>> diff --git a/.travis.yml b/.travis.yml

>     >>>> index 03e61b18..363c1b3f 100644

>     >>>> --- a/.travis.yml

>     >>>> +++ b/.travis.yml

>     >>>> @@ -25,7 +25,7 @@ before_install:

>     >>>>

>     >>>>  #       Install cunit for the validation tests because distro

>     version

>     >>>> is too old and fails C99 compile

>     >>>>          - export CUNIT_VERSION=2.1-3

>     >>>> -        - curl -sSOL

>     >>>>

>     http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>     <http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2>

>     >>>> +        - for _ in {1..10}; do

>     >>>>

>     http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

>     <http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2>

>     >>>> && break; sleep 1; done

>     >>>

>     >>> If we're going to make this more robust, what happens if the 10

>     >>> attempts all fail? Do we just run off the rails as before or make an

>     >>> attempt to quit with some sort of useful debug msg?

>     >>>

>     >>>>          - tar -jxf *.bz2

>     >>>>          - cd CUnit*

>     >>>>          - ./bootstrap

>     >>>> --

>     >>>> 2.11.0.295.gd7dffce

>     >>>>

>     >>

>     >>

>     >>

>     >>

>     >> --

>     >> Mike Holmes

>     >> Program Manager - Linaro Networking Group

>     >> Linaro.org │ Open source software for ARM SoCs

>     >> "Work should be fun and collaborative, the rest follows"

>     >>

>     >>

> 

> 

> 

> 

> -- 

> Mike Holmes

> Program Manager - Linaro Networking Group

> Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM SoCs

> "Work should be fun and collaborative, the rest follows"

> 

> __

> 

>
Mike Holmes Jan. 30, 2017, 3:14 p.m. | #8
On 30 January 2017 at 10:11, Maxim Uvarov <maxim.uvarov@linaro.org> wrote:

> On 01/30/17 17:57, Mike Holmes wrote:

> >

> >

> > On 30 January 2017 at 09:47, Maxim Uvarov <maxim.uvarov@linaro.org

> > <mailto:maxim.uvarov@linaro.org>> wrote:

> >

> >     On 01/30/17 17:38, Bill Fischofer wrote:

> >     > On Mon, Jan 30, 2017 at 8:30 AM, Mike Holmes <

> mike.holmes@linaro.org <mailto:mike.holmes@linaro.org>> wrote:

> >     >> Currently we have forked the repo and we pull from that copy,

> that copy is

> >     >> on Anders poeple.linaro.org <http://poeple.linaro.org> for the

> internal Jenkins CI

> >     >>

> >     >> Maybe we add cunit fork to the lng offical repo location so that

> we can do

> >     >> this from github also and not  have to point at a personal

> location ?

> >     >

> >     > If we're going to fork, agree we should do so "officially" rather

> than

> >     > in a personal repo.

> >     >

> >

> >     CUnit is in svn, so it will not be clean fork. We can put tar.gz to

> some

> >     repo. But for now I would increase number of tries.

> >

> >

> > It is so easy to push the tar and then there is never an issue, I think

> > that would be better for internal CI so I will check with Anders and try

> > to move that at least.

> >

>

> we also need account 2 things:

>

> a) we should do exactly what is said in our README.

> b) we should use official repo. If it's dead other people also can not

> build odp. If we mirror it we should update README.

>

> If we said that we support:

>

> apt-get install libcunit1-dev

>

> then maybe get rid text from DEPENDANCIES about building it from src?

> People should know where to get it if they build it from src.

>

> Maxim.

>

>

Good points


> >

> >

> >     Maxim.

> >

> >

> >     >>

> >     >> Mike

> >     >>

> >     >> On 29 January 2017 at 17:03, Bill Fischofer

> >     <bill.fischofer@linaro.org <mailto:bill.fischofer@linaro.org>>

> >     >> wrote:

> >     >>>

> >     >>> On Fri, Jan 27, 2017 at 1:21 PM, Maxim Uvarov

> >     <maxim.uvarov@linaro.org <mailto:maxim.uvarov@linaro.org>>

> >     >>> wrote:

> >     >>>> some time curl fails to download cunit from sf.net

> >     <http://sf.net> or it's

> >     >>>> mirrors. Try 10 times with 1 second delay.

> >     >>>>

> >     >>>> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org

> >     <mailto:maxim.uvarov@linaro.org>>

> >     >>>> ---

> >     >>>>  .travis.yml | 2 +-

> >     >>>>  1 file changed, 1 insertion(+), 1 deletion(-)

> >     >>>>

> >     >>>> diff --git a/.travis.yml b/.travis.yml

> >     >>>> index 03e61b18..363c1b3f 100644

> >     >>>> --- a/.travis.yml

> >     >>>> +++ b/.travis.yml

> >     >>>> @@ -25,7 +25,7 @@ before_install:

> >     >>>>

> >     >>>>  #       Install cunit for the validation tests because distro

> >     version

> >     >>>> is too old and fails C99 compile

> >     >>>>          - export CUNIT_VERSION=2.1-3

> >     >>>> -        - curl -sSOL

> >     >>>>

> >     http://sourceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> >     <http://sourceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2>

> >     >>>> +        - for _ in {1..10}; do

> >     >>>>

> >     http://souirceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2

> >     <http://souirceforge.net/projects/cunit/files/CUnit/${

> CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2>

> >     >>>> && break; sleep 1; done

> >     >>>

> >     >>> If we're going to make this more robust, what happens if the 10

> >     >>> attempts all fail? Do we just run off the rails as before or

> make an

> >     >>> attempt to quit with some sort of useful debug msg?

> >     >>>

> >     >>>>          - tar -jxf *.bz2

> >     >>>>          - cd CUnit*

> >     >>>>          - ./bootstrap

> >     >>>> --

> >     >>>> 2.11.0.295.gd7dffce

> >     >>>>

> >     >>

> >     >>

> >     >>

> >     >>

> >     >> --

> >     >> Mike Holmes

> >     >> Program Manager - Linaro Networking Group

> >     >> Linaro.org │ Open source software for ARM SoCs

> >     >> "Work should be fun and collaborative, the rest follows"

> >     >>

> >     >>

> >

> >

> >

> >

> > --

> > Mike Holmes

> > Program Manager - Linaro Networking Group

> > Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM

> SoCs

> > "Work should be fun and collaborative, the rest follows"

> >

> > __

> >

> >

>

>



-- 
Mike Holmes
Program Manager - Linaro Networking Group
Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
"Work should be fun and collaborative, the rest follows"

Patch

diff --git a/.travis.yml b/.travis.yml
index 03e61b18..363c1b3f 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -25,7 +25,7 @@  before_install:
 
 #       Install cunit for the validation tests because distro version is too old and fails C99 compile
         - export CUNIT_VERSION=2.1-3
-        - curl -sSOL http://sourceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2
+        - for _ in {1..10}; do http://souirceforge.net/projects/cunit/files/CUnit/${CUNIT_VERSION}/CUnit-${CUNIT_VERSION}.tar.bz2 && break; sleep 1; done
         - tar -jxf *.bz2
         - cd CUnit*
         - ./bootstrap