January 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 64 bit VM build problems: gl.h not found, or glRenderer conflicts

by Eliot Miranda

Hi Alistair, > On Jan 25, 2018, at 11:54 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi, > > I'm attempting to build the 64 bit VM in a docker container on Ubuntu > 16.04 installing the required packages using > opensmalltalk-vm/.travis_install.sh, however B3DAcceleratorPlugin > fails to build because it can't find gl.h. > > Installing mesa-common-dev (which is the most common answer when > searching for missing gl.h on google) changes the error to glRenderer > is redefined and has conflicting types. > > Does anyone know what the correct combination of packages is? The information is supposed to be towards the bottom of build.linux64x64 so if it's missing and you find it please remember to add it there. > > Thanks! > Alistair >

Jan. 26, 2018

[Pharo 7.0-dev] Build #459: 21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #459 was: FAILURE. The Pull Request #724 was integrated: "21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest" Pull request url: https://github.com/pharo-project/pharo/pull/724 Issue Url: https://pharo.fogbugz.com/f/cases/21107 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 26, 2018

Re: [Pharo-dev] CI Hickups ...

by Marcus Denker

> On 26 Jan 2018, at 14:42, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > > >> On Jan 26, 2018, at 09:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hello, >> >> Yesâ¦ I try to make notes about all failing test so we can detect patterns >> > > Will you share the notes? > Here are some from todays reviews: testPatch â MacOS32.Zinc.Tests.ZnClientTests Failed to start server on port 1719. Is there one already? testTwiceDeliveredDataSholdBeDetected â MacOS32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testTwiceDeliveredDataSholdBeDetected â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testDeliverNow3 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testDeliverNow2 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testAddCollector3 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testNotDeliveredDataShouldBeResent â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest testGetPharoVersion â MacOS32.Zinc.Zodiac.ZnHTTPSTests testExecuteOnceAfterSchedulingMultipleTimes â MacOS32.OmbuTests.OmDeferrerTest

Jan. 26, 2018

Re: [Pharo-dev] CI Hickups ...

by Juraj Kubelka

> On Jan 26, 2018, at 09:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > Yesâ¦ I try to make notes about all failing test so we can detect patterns > Will you share the notes? > It seems most of them are related to timing issues that come from the fact that > it runs on a virtualised boxâ¦ > Others are related to the fact that we run multiple instances in parallel on the > same machine and they try to open the same port. (not that often). That part can be fixed using port 0 in corresponding test cases. It opens a free port. Cheers, Juraj > > Another problem is that the vm sometimes crashes (related to the font rendering bug) > > We really need to try to find a way to stabilise the CI. > > Marcus > >> On 26 Jan 2018, at 10:23, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> While our general build from Pharo 7 is (more or less often) green >> >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >> >> I've noticed more and more that the CI builds for the PR's to Pharo 7 even for trivial changes are >> often broken and not green >> >> https://github.com/pharo-project/pharo/pulls >> >> which is annoying and one still has the feeling to break the builds. >> >> As always I think getting a more stable CI is dependent on time, resources and priorities. But does anyone know >> if this is a general issue or something that is already worked on? >> >> Thx >> T. >> > >

Jan. 26, 2018

[Pharo 7.0-dev] Build #458: 20905-upToAll-for-ZnCharacterReadStream

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #458 was: SUCCESS. The Pull Request #634 was integrated: "20905-upToAll-for-ZnCharacterReadStream" Pull request url: https://github.com/pharo-project/pharo/pull/634 Issue Url: https://pharo.fogbugz.com/f/cases/20905 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 26, 2018

[Pharo 7.0-dev] Build #457: 21121-Use-assertequals-in-TimespanTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #457 was: SUCCESS. The Pull Request #743 was integrated: "21121-Use-assertequals-in-TimespanTest" Pull request url: https://github.com/pharo-project/pharo/pull/743 Issue Url: https://pharo.fogbugz.com/f/cases/21121 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 26, 2018

Re: [Pharo-dev] CI Hickups ...

by Marcus Denker

Hello, Yesâ¦ I try to make notes about all failing test so we can detect patterns It seems most of them are related to timing issues that come from the fact that it runs on a virtualised boxâ¦ Others are related to the fact that we run multiple instances in parallel on the same machine and they try to open the same port. (not that often). Another problem is that the vm sometimes crashes (related to the font rendering bug) We really need to try to find a way to stabilise the CI. Marcus > On 26 Jan 2018, at 10:23, Torsten Bergmann <astares(a)gmx.de> wrote: > > While our general build from Pharo 7 is (more or less often) green > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > I've noticed more and more that the CI builds for the PR's to Pharo 7 even for trivial changes are > often broken and not green > > https://github.com/pharo-project/pharo/pulls > > which is annoying and one still has the feeling to break the builds. > > As always I think getting a more stable CI is dependent on time, resources and priorities. But does anyone know > if this is a general issue or something that is already worked on? > > Thx > T. >

Jan. 26, 2018

Re: [Pharo-dev] 64 bit VM build problems: gl.h not found, or glRenderer conflicts

by K K Subbu

On Ubuntu 16.04, I had to use: sudo apt-get install uuid-dev libcairo2-dev libpango1.0-dev libgl1-mesa-dev libgl1-mesa-glx to get all dependencies. This was sometime ago and the change should have made it to build.linux64x64/HowToBuild by now. What exactly is your error message? Regards .. Subbu On Friday 26 January 2018 01:24 AM, Alistair Grant wrote: > Hi, > > I'm attempting to build the 64bit VM in a docker container on Ubuntu > 16.04 installing the required packages using > opensmalltalk-vm/.travis_install.sh, however B3DAcceleratorPlugin > fails to build because it can't find gl.h. > > Installing mesa-common-dev (which is the most common answer when > searching for missing gl.h on google) changes the error to glRenderer > is redefined and has conflicting types. > > Does anyone know what the correct combination of packages is? > > Thanks! > Alistair >

Jan. 26, 2018

[Pharo 7.0-dev] Build #456: 20057-Autocomplete-crashes-for-trait-methods

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #456 was: SUCCESS. The Pull Request #707 was integrated: "20057-Autocomplete-crashes-for-trait-methods" Pull request url: https://github.com/pharo-project/pharo/pull/707 Issue Url: https://pharo.fogbugz.com/f/cases/20057 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 26, 2018

[Pharo 7.0-dev] Build #455: 21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #455 was: SUCCESS. The Pull Request #727 was integrated: "21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest" Pull request url: https://github.com/pharo-project/pharo/pull/727 Issue Url: https://pharo.fogbugz.com/f/cases/21104 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 26, 2018