Re: [Pharo-dev] CI Down

[Guillermo Polito]

This afternoon we were notified that everything is UP again. Not
necessarily stable but UP.

On Wed, Aug 8, 2018 at 6:38 PM Martin Dias  wrote:

>
>
> El mié., 8 de ago. de 2018 05:44, Norbert Hartl 
> escribió:
>
>> Might be but doing make in the pharo repo gives you this
>>
>
> hm... we should check that dependency. Epicea, Ombu and Hiedra packages
> should be versioned in pharo repo.
>
>
>> …
>> Project: Hermes baseline
>> Project: Ficus 0.3.8
>> ...RETRY->Hiedra
>> ...RETRY->Hiedra
>> gofer repository error: 'GoferRepositoryError: Could not access
>> http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut:
>> Cannot connect to 128.93.162.53:80'...ignoring
>> ...FAILED->Hiedra'Errors in script loaded from
>> /Users/norbert/play/iot/pharo/bootstrap/scripts/prepare_image.st'
>> Could not resolve: Hiedra [Hiedra] in
>> /Users/norbert/play/iot/pharo/pharo-local/package-cache
>> http://smalltalkhub.com/mc/MartinDias/Ficus/main/ ERROR:
>> ‚GoferRepositoryError: Could not access
>> http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut:
>> Cannot connect to 128.93.162.53:80'
>> …
>>
>>
>> Am 08.08.2018 um 11:21 schrieb Esteban Lorenzano :
>>
>> I was convinced that Epicea was now managed inside Pharo.
>>
>> On 8 Aug 2018, at 11:15, Norbert Hartl  wrote:
>>
>> The one thing is not be able to run the CI. The bigger problem is that
>> pharo is not buildable at all. Can we please move mission critical repos
>> like epicea to github?
>>
>> Norbert
>>
>> Am 08.08.2018 um 09:55 schrieb Guillermo Polito <
>> guillermopol...@gmail.com>:
>>
>> Hi all,
>>
>> Since yesterday evening, CI is down because of Inria network problems at
>> the level of Paris.
>> Inria tells us that they do not have yet an estimation of how much time
>> it will take to fix it.
>>
>> Until then, there will be no CI testing PRs nor new builds.
>> Previous Pharo builds are still available in http://files.pharo.org/,
>> which is hosted in OVH.
>>
>> I'll keep you updated,
>> Guille
>>
>>
>>
>>
>>

-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

Re: [Pharo-dev] CI Down

[Martin Dias]

El mié., 8 de ago. de 2018 05:44, Norbert Hartl 
escribió:

> Might be but doing make in the pharo repo gives you this
>

hm... we should check that dependency. Epicea, Ombu and Hiedra packages
should be versioned in pharo repo.


> …
> Project: Hermes baseline
> Project: Ficus 0.3.8
> ...RETRY->Hiedra
> ...RETRY->Hiedra
> gofer repository error: 'GoferRepositoryError: Could not access
> http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut:
> Cannot connect to 128.93.162.53:80'...ignoring
> ...FAILED->Hiedra'Errors in script loaded from
> /Users/norbert/play/iot/pharo/bootstrap/scripts/prepare_image.st'
> Could not resolve: Hiedra [Hiedra] in
> /Users/norbert/play/iot/pharo/pharo-local/package-cache
> http://smalltalkhub.com/mc/MartinDias/Ficus/main/ ERROR:
> ‚GoferRepositoryError: Could not access
> http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut:
> Cannot connect to 128.93.162.53:80'
> …
>
>
> Am 08.08.2018 um 11:21 schrieb Esteban Lorenzano :
>
> I was convinced that Epicea was now managed inside Pharo.
>
> On 8 Aug 2018, at 11:15, Norbert Hartl  wrote:
>
> The one thing is not be able to run the CI. The bigger problem is that
> pharo is not buildable at all. Can we please move mission critical repos
> like epicea to github?
>
> Norbert
>
> Am 08.08.2018 um 09:55 schrieb Guillermo Polito  >:
>
> Hi all,
>
> Since yesterday evening, CI is down because of Inria network problems at
> the level of Paris.
> Inria tells us that they do not have yet an estimation of how much time it
> will take to fix it.
>
> Until then, there will be no CI testing PRs nor new builds.
> Previous Pharo builds are still available in http://files.pharo.org/,
> which is hosted in OVH.
>
> I'll keep you updated,
> Guille
>
>
>
>
>

Re: [Pharo-dev] CI Down

[Norbert Hartl]

Might be but doing make in the pharo repo gives you this

…
Project: Hermes baseline
Project: Ficus 0.3.8
...RETRY->Hiedra
...RETRY->Hiedra
gofer repository error: 'GoferRepositoryError: Could not access 
http://smalltalkhub.com/mc/MartinDias/Epicea/main/: ConnectionTimedOut: Cannot 
connect to 128.93.162.53:80'...ignoring
...FAILED->Hiedra'Errors in script loaded from 
/Users/norbert/play/iot/pharo/bootstrap/scripts/prepare_image.st'
Could not resolve: Hiedra [Hiedra] in 
/Users/norbert/play/iot/pharo/pharo-local/package-cache 
http://smalltalkhub.com/mc/MartinDias/Ficus/main/ ERROR: ‚GoferRepositoryError: 
Could not access http://smalltalkhub.com/mc/MartinDias/Epicea/main/: 
ConnectionTimedOut: Cannot connect to 128.93.162.53:80'
…


> Am 08.08.2018 um 11:21 schrieb Esteban Lorenzano :
> 
> I was convinced that Epicea was now managed inside Pharo.
> 
>> On 8 Aug 2018, at 11:15, Norbert Hartl > > wrote:
>> 
>> The one thing is not be able to run the CI. The bigger problem is that pharo 
>> is not buildable at all. Can we please move mission critical repos like 
>> epicea to github? 
>> 
>> Norbert
>> 
>>> Am 08.08.2018 um 09:55 schrieb Guillermo Polito >> >:
>>> 
>>> Hi all,
>>> 
>>> Since yesterday evening, CI is down because of Inria network problems at 
>>> the level of Paris.
>>> Inria tells us that they do not have yet an estimation of how much time it 
>>> will take to fix it.
>>> 
>>> Until then, there will be no CI testing PRs nor new builds.
>>> Previous Pharo builds are still available in http://files.pharo.org/ 
>>> , which is hosted in OVH.
>>> 
>>> I'll keep you updated,
>>> Guille
>> 
> 

Re: [Pharo-dev] CI Down

[Esteban Lorenzano]

I was convinced that Epicea was now managed inside Pharo.

> On 8 Aug 2018, at 11:15, Norbert Hartl  wrote:
> 
> The one thing is not be able to run the CI. The bigger problem is that pharo 
> is not buildable at all. Can we please move mission critical repos like 
> epicea to github? 
> 
> Norbert
> 
>> Am 08.08.2018 um 09:55 schrieb Guillermo Polito > >:
>> 
>> Hi all,
>> 
>> Since yesterday evening, CI is down because of Inria network problems at the 
>> level of Paris.
>> Inria tells us that they do not have yet an estimation of how much time it 
>> will take to fix it.
>> 
>> Until then, there will be no CI testing PRs nor new builds.
>> Previous Pharo builds are still available in http://files.pharo.org/ 
>> , which is hosted in OVH.
>> 
>> I'll keep you updated,
>> Guille
> 

Re: [Pharo-dev] CI Down

[Esteban Lorenzano]

Also, this problems includes smalltalkhub :(

Esteban

(Good moment to remember all that we have good git support now :P)

> On 8 Aug 2018, at 09:55, Guillermo Polito  wrote:
> 
> Hi all,
> 
> Since yesterday evening, CI is down because of Inria network problems at the 
> level of Paris.
> Inria tells us that they do not have yet an estimation of how much time it 
> will take to fix it.
> 
> Until then, there will be no CI testing PRs nor new builds.
> Previous Pharo builds are still available in http://files.pharo.org/ 
> , which is hosted in OVH.
> 
> I'll keep you updated,
> Guille

Re: [Pharo-dev] CI Down

[Norbert Hartl]

The one thing is not be able to run the CI. The bigger problem is that pharo is 
not buildable at all. Can we please move mission critical repos like epicea to 
github? 

Norbert

> Am 08.08.2018 um 09:55 schrieb Guillermo Polito :
> 
> Hi all,
> 
> Since yesterday evening, CI is down because of Inria network problems at the 
> level of Paris.
> Inria tells us that they do not have yet an estimation of how much time it 
> will take to fix it.
> 
> Until then, there will be no CI testing PRs nor new builds.
> Previous Pharo builds are still available in http://files.pharo.org/ 
> , which is hosted in OVH.
> 
> I'll keep you updated,
> Guille

Re: [Pharo-dev] CI down this morning for maintance

[Marcus Denker]

Everything is online again!

> On 16 Feb 2017, at 10:22, Marcus Denker  wrote:
> 
> Hi,
> 
> The ci (pharo and pharo-contrib) has some maintenance this morning and can be 
> down for some
> hours. 
> 
>   Marcus