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
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 <guillermopolito@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/ <http://files.pharo.org/>, which is hosted in OVH.
I'll keep you updated, Guille
I was convinced that Epicea was now managed inside Pharo.
On 8 Aug 2018, at 11:15, Norbert Hartl <norbert@hartl.name> 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 <guillermopolito@gmail.com <mailto:guillermopolito@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/ <http://files.pharo.org/>, which is hosted in OVH.
I'll keep you updated, Guille
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 <estebanlm@gmail.com>:
I was convinced that Epicea was now managed inside Pharo.
On 8 Aug 2018, at 11:15, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> 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 <guillermopolito@gmail.com <mailto:guillermopolito@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/ <http://files.pharo.org/>, which is hosted in OVH.
I'll keep you updated, Guille
El mié., 8 de ago. de 2018 05:44, Norbert Hartl <norbert@hartl.name> 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 <estebanlm@gmail.com>:
I was convinced that Epicea was now managed inside Pharo.
On 8 Aug 2018, at 11:15, Norbert Hartl <norbert@hartl.name> 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 <guillermopolito@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
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 <tinchodias@gmail.com> wrote:
El mié., 8 de ago. de 2018 05:44, Norbert Hartl <norbert@hartl.name> 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 <estebanlm@gmail.com>:
I was convinced that Epicea was now managed inside Pharo.
On 8 Aug 2018, at 11:15, Norbert Hartl <norbert@hartl.name> 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 < guillermopolito@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 <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13
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 <guillermopolito@gmail.com> 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/ <http://files.pharo.org/>, which is hosted in OVH.
I'll keep you updated, Guille
participants (4)
-
Esteban Lorenzano -
Guillermo Polito -
Martin Dias -
Norbert Hartl