- Pharo-dev - lists.pharo.org

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

CI Hickups ...

by Torsten Bergmann

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] [ANN] Next Pharo release moved to end of year

by Stephane Ducasse

Hi I'm starting to tag issue with difficulty-Easy Stef On Wed, Jan 24, 2018 at 10:21 AM, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi Esteban, > > If it would possible to identify some tickets in FogBuz affordable for less > expererienced smalltalkers, > I think several devs here at Osoco (and other organizations) could > contribute with the Pharo development. > > I know It would be a small help, but it's better than nothing. > > Rafa > > 2018-01-23 18:54 GMT+00:00 Stephan Eggermont <stephan(a)stack.nl>: >> >> Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> > Hi all, >> > >> > After some analysis of current condition of development, we decided to >> > move the upcoming release to end of the year (and not May, as usual). >> >> Thanks for the clear and timely decision. Having to delay is never nice, >> but with a high innovation rate comes a higher risk. Denial helps noone, >> keep up the good work! >> >> Stephan >> >> >> >> >> >

Jan. 26, 2018

Re: [Pharo-dev] [Issue Tracker] Problem with Spam

by Marcus Denker

I have not yet found a way to do it. https://forum.manuscript.com/t/dozens-of-spam-emails-a-day-how-do-i-turn-of… <https://forum.manuscript.com/t/dozens-of-spam-emails-a-day-how-do-i-turn-of…> > On 26 Jan 2018, at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > I guess these are anonymous submissions ? > Can't this (for now at least) not be restricted to actual users that need to authenticate first ? > >> On 26 Jan 2018, at 10:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> Since some days we get ~20 spam cases per day on the issue tracker. >> >> -> I have asked on the Forums what we can do >> -> As long as there is no solution, I am closing them the morning. >> >> Marcus >> > >

Jan. 26, 2018