- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1279: 22498-TextEditorsaveContentsInFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 30, 2018

Sept. 30, 2018

There is a new Pharo build available! The status of the build #1279 was: FAILURE. The Pull Request #1839 was integrated: "22498-TextEditorsaveContentsInFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1839 Issue Url: https://pharo.fogbugz.com/f/cases/22498 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1278: 22397-Add-executable-comments-to-Date-classes
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

There is a new Pharo build available! The status of the build #1278 was: SUCCESS. The Pull Request #1832 was integrated: "22397-Add-executable-comments-to-Date-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1832 Issue Url: https://pharo.fogbugz.com/f/cases/22397 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1277: 22497-MIMEDocumentsaveToFile-should-not-use-FileStream
by ci-pharo-ci-jenkins2＠inria.fr Sept. 29, 2018

Sept. 29, 2018

There is a new Pharo build available! The status of the build #1277 was: SUCCESS. The Pull Request #1838 was integrated: "22497-MIMEDocumentsaveToFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1838 Issue Url: https://pharo.fogbugz.com/f/cases/22497 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Artifact and PDFExporter for Roassal
by milton mamani Sept. 28, 2018

Sept. 28, 2018

El jue., 13 sept. 2018 a las 14:06, milton mamani (<akevalion(a)gmail.com>) escribiÃ³: > Hi! > > I am Milton Mamani I work with Roassal2, and now I am in ESUG-Cagliari, > and I have tried to load Artefact with the next piece of code, in the last > Pharo7 image. > > Metacello new > configuration: 'Artefact'; > smalltalkhubUser: 'RMoD' project: 'Artefact'; > version: #stable; > load. > > "To load roassal and pdf roassal exporter" > > Metacello new > configuration: 'GraphQLBeta'; > smalltalkhubUser: 'ObjectProfile' project: 'GraphQL'; > version: #development; > load. > > Gofer new > smalltalkhubUser: 'azazael' project: 'RTPDFExporter'; > package: 'ConfigurationOfRTPDFExporter'; load. > (Smalltalk at: #ConfigurationOfRTPDFExporter) loadDevelopment > > I have a problem, when I tried to export my Roassal-Visualization to pdf > file with for example this piece of code: > > view := RTBoxPlotExample new exampleBoxPlot5 build view. > stream := 'foo.pdf' asFileReference writeStream. > > [RTPDFExporter new > stream: stream; > exportView: view ] ensure: [ stream close ] > > I get a lot of kind exceptions related with the class: PDFStreamPrinter > > In the method visitPDFDataXRefEntry: > And in the logic of the new Stream classes of Pharo7. > > Could you please review Artifact in Pharo7 with this roassal2 > implementation > > Cheers, > Milton > >

3 2

[Pharo 7.0-dev] Build #1276: 22482-AutoCompletion-preview-breaks-code-navigation
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1276 was: SUCCESS. The Pull Request #1831 was integrated: "22482-AutoCompletion-preview-breaks-code-navigation" Pull request url: https://github.com/pharo-project/pharo/pull/1831 Issue Url: https://pharo.fogbugz.com/f/cases/22482 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1275: 22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1275 was: FAILURE. The Pull Request #1829 was integrated: "22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration" Pull request url: https://github.com/pharo-project/pharo/pull/1829 Issue Url: https://pharo.fogbugz.com/f/cases/22480 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1274: 22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files
by ci-pharo-ci-jenkins2＠inria.fr Sept. 28, 2018

Sept. 28, 2018

There is a new Pharo build available! The status of the build #1274 was: FAILURE. The Pull Request #1806 was integrated: "22458-lastFileFor-baseFileName-extension-extension-randomly-sorts-files" Pull request url: https://github.com/pharo-project/pharo/pull/1806 Issue Url: https://pharo.fogbugz.com/f/cases/22458 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

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