> On 20 Feb 2018, at 14:05, Marcus Denker <[email protected]> wrote: > > > >> On 20 Feb 2018, at 13:31, [email protected] >> <mailto:[email protected]> wrote: >> >> There is a new Pharo build available! >> >> The status of the build #580 was: FAILURE. >> >> The Pull Request #893 was integrated: "21350 Enhance LibC with piping and >> the platform with running commands" >> Pull request url: https://github.com/pharo-project/pharo/pull/893 >> <https://github.com/pharo-project/pharo/pull/893> >> >> Issue Url: https://pharo.fogbugz.com/f/cases/21350 >> <https://pharo.fogbugz.com/f/cases/21350> >> Build Url: >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/580/ >> >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/580/> > > [kernel-unix-32] Downloading the latest pharoVM: > [kernel-unix-32] > http://files.pharo.org/get-files/70/pharo-linux-stable.zip > <http://files.pharo.org/get-files/70/pharo-linux-stable.zip> > [kernel-unix-32] mkdir: cannot create directory ‘pharo-vm’: File exists >
I triggered the CI job that actually updates get.pharo.org <http://get.pharo.org/> —> this should not happen anymore Marcus
