> On 19 Feb 2018, at 12:23, ci-pharo-ci-jenki...@inria.fr wrote:
>
> There is a new Pharo build available!
>
> The status of the build #574 was: FAILURE.
>
> The Pull Request #912 was integrated:
> "21226-GLMMorphicText-sents-unknown-secondClock"
> Pull request url: https://github.com/pharo-project/pharo/pull/912
>
> Issue Url: https://pharo.fogbugz.com/f/cases/21226
> Build Url:
> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/574/
Downloading the latest pharoVM:
http://files.pharo.org/get-files/70/pharo-linux-stable.zip
mkdir: cannot create directory ‘pharo-vm’: File exists
I really wonder why it does that *sometimes*, but in most cases it works?
=> we should do the workaround:
https://pharo.fogbugz.com/f/cases/21255/Zeroconf-script-should-re-use-existing-directories
This will not fix the real reason, but I think is would be a good thing in
general to make the zeroconf
scripts just update existing downloads.
Marcus
