There is a new Pharo build available!
The status of the build #594 was: FAILURE. The Pull Request #928 was integrated: "21387-Fixing-some-tests-when-turning-on-Read-only-literals" Pull request url: https://github.com/pharo-project/pharo/pull/928 Issue Url: https://pharo.fogbugz.com/f/cases/21387 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/594/ |
> On 22 Feb 2018, at 14:55, [hidden email] wrote: > > There is a new Pharo build available! > > The status of the build #594 was: FAILURE. > > The Pull Request #928 was integrated: "21387-Fixing-some-tests-when-turning-on-Read-only-literals" > Pull request url: https://github.com/pharo-project/pharo/pull/928 > > Issue Url: https://pharo.fogbugz.com/f/cases/21387 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/594/ this is the case where we used to get the error that the vm directory already exists. Now it look like this: Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo-linux-stable.zip replace pharo-vm/lib/pharo/5.0-201708271955/libssh2.so.1.0.1? [y]es, [n]o, [A]ll, [N]one, [r]ename: new name: replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [{ENTER}] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [if [ "$OS] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [" == "win] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [" ]; then] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [{ENTER}] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [ PHARO] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [_VM=`find] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [ $VM_DIR ] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [-name ${V] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: error: invalid response [M_BINARY_] replace pharo-vm/M_DIR/vm.zip? [y]es, [n]o, [A]ll, [N]one, [r]ename: ++ find bootstrap-cache -name 'Pharo7.0-bootstrap-32bit-*.zip' + IMAGE_ARCHIVE=bootstrap-cache/Pharo7.0-bootstrap-32bit-62fe456.zip + unzip bootstrap-cache/Pharo7.0-bootstrap-32bit-62fe456.zip Archive: bootstrap-cache/Pharo7.0-bootstrap-32bit-62fe456.zip inflating: Pharo7.0-bootstrap-32bit-62fe456.image ++ find . -name Pharo7.0-bootstrap-32bit-62fe456.image + IMAGE_FILE=./Pharo7.0-bootstrap-32bit-62fe456.image ++ find bootstrap-cache -name 'Pharo7.0-hermesPackages-32bit-*.zip' + HERMES_ARCHIVE=bootstrap-cache/Pharo7.0-hermesPackages-32bit-62fe456.zip + unzip bootstrap-cache/Pharo7.0-hermesPackages-32bit-62fe456.zip Archive: bootstrap-cache/Pharo7.0-hermesPackages-32bit-62fe456.zip inflating: OpalCompiler-Core.hermes inflating: CodeExport.hermes inflating: CodeImport.hermes inflating: CodeImportCommandLineHandlers.hermes inflating: SUnit-Core.hermes inflating: JenkinsTools-Core.hermes inflating: SUnit-Tests.hermes inflating: Hermes-Extensions.hermes ++ find bootstrap-cache -name 'Pharo7.0-rpackage-32bit-*.zip' + RPACKAGE_ARCHIVE=bootstrap-cache/Pharo7.0-rpackage-32bit-62fe456.zip + unzip bootstrap-cache/Pharo7.0-rpackage-32bit-62fe456.zip Archive: bootstrap-cache/Pharo7.0-rpackage-32bit-62fe456.zip inflating: protocolsKernel.txt inflating: packagesKernel.txt + mv ./Pharo7.0-bootstrap-32bit-62fe456.image bootstrap.image + export PHARO_CI_TESTING_ENVIRONMENT=1 + PHARO_CI_TESTING_ENVIRONMENT=1 + ./pharo bootstrap.image bootstrap/scripts/runKernelTests.sh: line 34: ./pharo: No such file or directory |
Free forum by Nabble | Edit this page |