It was a strange failure during the image cleanup, I guess it was related to the FuelPlatform-Pharo-Core package issue which is now fixed.
-- Pavel 2017-11-03 13:48 GMT+01:00 Norbert Hartl <[email protected]>: > Maybe that is the reason the status is considered a FAILURE? > > Norbert > > > Am 03.11.2017 um 13:44 schrieb Torsten Bergmann <[email protected]>: > > > > This build number is red: > > > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/ > > > > > >> Gesendet: Freitag, 03. November 2017 um 13:16 Uhr > >> Von: [email protected] > >> An: [email protected] > >> Betreff: [Pharo-dev] [Pharo 7.0-dev] Build #253: > 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings > >> > >> There is a new Pharo build available! > >> > >> The status of the build #253 was: FAILURE. > >> > >> The Pull Request #426 was integrated: "20628-Categories-definition- > in-exported-Tonel-must-be-symbols-not-strings" > >> Pull request url: https://github.com/pharo-project/pharo/pull/426 > >> > >> Issue Url: https://pharo.fogbugz.com/f/cases/20628 > >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/253/ > >> > >
