- Pharo-dev - lists.pharo.org

PharoLauncher based test resporting centre
by Ben Coman Sept. 28, 2018

Sept. 28, 2018

Just a random idea... when running Testrunner locally and a random test causes the image to freeze, its a bit of an effort to identify which test was being run. You need to restart and then start bisecting the tests and perhaps it is intermittent so the bisect doesn't work... but now that PharoLauncher has been mainstreamed maybe it could provide a centralised Reporting Centre i.e. open a port for launched images to report the test about-to-commence as well as the run time. Then it would be simple to see which test froze the system. Also it could keep a record individual test runtimes, to alleviate fears when the system is not frozen but just a long running test. Extending the idea, while CI testing is very useful, we get these sporadic errors that are hard to replicate locally. A local PharoLauncher driven system for repetitively launching an image auto-running tests might be good to gather statistics on sporadic failures to then drill down on the troublemakers. Plus with the goal of having an object based logging system, a viewer is needed and perhaps PharoLauncher would be a logical place to provide a logging service to gather and especially to view log-objects reporting by launched images. of course, resources required to do it, but just thought I share the idea. cheers -ben

1 1

[Pharo 7.0-dev] Build #1273: 22477-DelayScheduler-cleanup-and-refactoring
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2018

Sept. 27, 2018

There is a new Pharo build available! The status of the build #1273 was: FAILURE. The Pull Request #1819 was integrated: "22477-DelayScheduler-cleanup-and-refactoring" Pull request url: https://github.com/pharo-project/pharo/pull/1819 Issue Url: https://pharo.fogbugz.com/f/cases/22477 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Migrated Artefact to GitHub
by Guillermo Polito Sept. 27, 2018

Sept. 27, 2018

Hi all, I've moved the Artefact library to GitHub ( https://github.com/pharo-contributions/Artefact) I've also made some changes to it in the way and made a 1.7.0 version with: - support for Pharo7 streams - a baseline So, people using Artifact, you can contribute through pull requests ^^, Guille -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

3 2

Esteban's ChangeLog week of 17 September 2018
by estebanlm＠gmail.com Sept. 27, 2018

Sept. 27, 2018

Hello! This is my weekly ChangeLog, from 17 September 2018 to 23 September 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=17/9/2018&to=23/9/2018 ChangeLog ========= 19 September 2018: ------------------ * I migrated all [pharo-ide](https://github.com/pharo-ide) projects to tonel format. Harder than it seems, it took me a good bunch of hours. But now is working. This will enhance work/fixes on Calypso. 18 September 2018: ------------------ * I just [fixed the CI for Calypso](https://github.com/pharo-ide/Calypso/issues/319) (it was failing for Pharo 7.0 because of problems when updating). Now I can start fixing real issues of it :) 17 September 2018: ------------------ * I backported/promoted a new stable vm for Pharo 6.1. This is the one that has been tested for Pharo 7.0alpha already for some time, so things should be fine. Current stable VM is from 2018-07-04 (yeah, eventually we will have a decent semver numbering, but for now this will have to be enough :P) cheers! Esteban

3 3

Top MenuBar does not auto follow font changes
by Sven Van Caekenberghe Sept. 27, 2018

Sept. 27, 2018

Hi, The Top MenuBar does not seem to auto follow font changes, although it picks them uppitiest when you hide/show the menu bar from the Settings. Sven

1 0

[Pharo 7.0-dev] Build #1272: 22490-It-seems-that-openFileStreamwritable-is-dead-code
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2018

Sept. 27, 2018

There is a new Pharo build available! The status of the build #1272 was: SUCCESS. The Pull Request #1827 was integrated: "22490-It-seems-that-openFileStreamwritable-is-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/1827 Issue Url: https://pharo.fogbugz.com/f/cases/22490 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Esteban Lorenzano Sept. 26, 2018

Sept. 26, 2018

> On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer Is a misleading message. It means merge was done, but for some reason (usually network problems), some tests failed to run. We are working on fix that (but you knowâ¦ time :P). Esteban > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Marcus Denker Sept. 26, 2018

Sept. 26, 2018

Hi, It means that the build for this one merge failedâ¦ build got much more stable over the last weeks, but we still sometimes have crashes (here it seems to be the text render bug) But this is undefended of the merge: the next build then will take this into account. > On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

[Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1271 was: FAILURE. The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/1823 Issue Url: https://pharo.fogbugz.com/f/cases/22483 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1270: 22221-Jump-to-next-keyword
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1270 was: SUCCESS. The Pull Request #1722 was integrated: "22221-Jump-to-next-keyword" Pull request url: https://github.com/pharo-project/pharo/pull/1722 Issue Url: https://pharo.fogbugz.com/f/cases/jump Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0