- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #836: 21825-Improve-Catalog-loading
by ci-pharo-ci-jenkins2＠inria.fr May 5, 2018

May 5, 2018

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

1 0

[Pharo 7.0-dev] Build #835: 21804-Creating-a-Package-from-Calypso-produces-DNU
by ci-pharo-ci-jenkins2＠inria.fr May 5, 2018

May 5, 2018

There is a new Pharo build available! The status of the build #835 was: SUCCESS. The Pull Request #1293 was integrated: "21804-Creating-a-Package-from-Calypso-produces-DNU" Pull request url: https://github.com/pharo-project/pharo/pull/1293 Issue Url: https://pharo.fogbugz.com/f/cases/21804 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #834: 21832 Small cleanups for Compression packages
by ci-pharo-ci-jenkins2＠inria.fr May 5, 2018

May 5, 2018

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

1 0

Aboud CI test retries
by Guillermo Polito May 4, 2018

May 4, 2018

Hi all, Initially the pharo build had tests that were failing randomly. To cope with that, we introduced a retry of the tests. Nowadays, this situation is actually very rare. Tests that fail, fail always, and randomly failing tests are not seen so often... This means however, that in the case that a test is persistently failing, we are (uselessly) retrying it, and making jobs take 10-15 minutes longer for nothing. I propose that we remove the retries. - This will speed up the builds that are green and only penalize those that are not green. - Remove stress from our servers (that we use to have a higher ratio builds/hour :)) - Randomly failing tests will just need to manually retry the build. But since green builds take now ~15-20 minutes, which is in the same order of magnitude of the retries, we only penalize the one that found the hiccup. Guille

2 3

<Programming> 2019: Call for Papers & Call for Workshop Proposals
by Fabio Niephaus May 4, 2018

May 4, 2018

<Programming> 2019 : The Art, Science, and Engineering of Programming April 1-4, 2019, Genova, Italy http://2019.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it <Programming> for short. <Programming> seeks for papers that advance knowledge of programming on any relevant topic, including programming practice and experience. Paper submissions and publications are handled by the the Art, Science, and Engineering of Programming journal (http://programming-journal.org) Accepted papers must be presented at the conference. ******************************************************** CALL FOR PAPERS ******************************************************** <Programming> 2019 accepts scholarly papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. PAPER SUBMISSIONS: June 1, 2018 URL FOR SUBMISSIONS: http://programming-journal.org/submission/ Submissions covering several areas of expertise are accepted, including but not limited to: â¢ General-purpose programming â¢ Distributed systems programming â¢ Parallel and multi-core programming â¢ Graphics and GPU programming â¢ Security programming â¢ User interface programming â¢ Database programming â¢ Visual and live programming â¢ Data mining and machine learning programming â¢ Interpreters, virtual machines and compilers â¢ Modularity and separation of concerns â¢ Model-based development â¢ Metaprogramming and reflection â¢ Testing and debugging â¢ Program verification â¢ Programming education â¢ Programming environments â¢ Social coding ******************************************************** CALL FOR WORKSHOP PROPOSALS ******************************************************** To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, <Programming> will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. WORKSHOP PROPOSAL SUBMISSIONS: First Deadline: July 1st, 2018 Second Deadline: September 1st, 2018 The duration of workshops is in general one day, but we encourage the submission of half-day workshop proposals on focused topics as well. In exceptional situations, e.g., for workshops that involve actual practice of programming-related activities, workshop organizers can request a 2 day workshop slot. If desired, the workshop proceedings can be published in the ACM Digital Library. ******************************************************** IMPORTANT DATES ******************************************************** Research paper submissions: June 1, 2019 Research paper first notifications: August 1, 2018 Research paper final notifications: September 7, 2018 Workshop proposals: July 1st, 2018 (first deadline) Workshop proposals: September 1st, 2018 (second deadline) ******************************************************** ORGANIZATION ******************************************************** General Chair: Davide Ancona, University of Genova Local Organizing Chair: Elena Zucca, University of Genova Program Chair: Matthew Flatt, University of Utah Organizing Committee: Walter Cazzola (Workshops Co-Chair), UniversitÃ degli Studi di Milano Stefan Marr (Workshops Co-Chair), University of Kent Fabio Niephaus (Publicity Co-Chair), Hasso Plattner Institute, University of Potsdam Tobias Pape (Web Technology Chair), Hasso Plattner Institute, University of Potsdam Program Committee: Mehdi Bagherzadeh, Oakland University Walter Cazzola, UniversitÃ degli Studi di Milano Ravi Chugh, University of Chicago Joeri De Koster, Vrije Universiteit Brussel Christos Dimoulas, Northwestern University Susan Eisenbach, Imperial College London Richard P. Gabriel, Dream Songs, Inc. & HPI Jeremy Gibbons, University of Oxford Michael Greenberg, Pomona College Philipp Haller, KTH Royal Institute of Technology Robert Hirschfeld, HPI, University of Potsdam Eunsuk Kang, Carnegie Mellon University Stephen Kell, University of Cambridge Stefan Marr, University of Kent Tamara Rezk, Inria Joshua Sunshine, Carnegie Mellon University Steffen Zschaler, King's College London ******************************************************** <Programming> 2019 is kindly supported by AOSA ******************************************************** For more information, visit http://2019.programming-conference.org

1 0

[Pharo 7.0-dev] Build #833: 21824-Remove-test-retries-in-CI
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2018

May 4, 2018

There is a new Pharo build available! The status of the build #833 was: SUCCESS. The Pull Request #1291 was integrated: "21824-Remove-test-retries-in-CI" Pull request url: https://github.com/pharo-project/pharo/pull/1291 Issue Url: https://pharo.fogbugz.com/f/cases/21824 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #832: 21822-Fix-Zn-Tests-due-to-encryptedgooglecom-moving
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2018

May 3, 2018

There is a new Pharo build available! The status of the build #832 was: SUCCESS. The Pull Request #1290 was integrated: "21822-Fix-Zn-Tests-due-to-encryptedgooglecom-moving" Pull request url: https://github.com/pharo-project/pharo/pull/1290 Issue Url: https://pharo.fogbugz.com/f/cases/21822 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #831: 21821-Integrate-Iceberg-075
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2018

May 3, 2018

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

1 0

Do we kill the catalog?
by Stephane Ducasse May 3, 2018

May 3, 2018

Hi guys What do we do with it? What alternatives? Stef

16 48

[Ann] Iceberg 0.7.5
by Guillermo Polito May 3, 2018

May 3, 2018

Time for the weekly Iceberg update. Iceberg 0.7.5. will be in the next Pharo build. Thanks to all brave users, issue reporters and contributors :). Key improvements: - Several improvements in metacello integration. (see #625, #664, #688 + more tests) - For those using CI, we think this release will also fix https://github.com/pharo-vcs/iceberg/issues/643 Infrastructure improvements: - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 - In the next release we plan to do a pass on 64 bits ** Pharo 6.1 backport ** - We plan to backport this version to Pharo 6.1 - Cyril has been using the development version of Iceberg on Pharo 6.1 for a couple of weeks now. - This plus the green CI encourages us to backport to Pharo 6.1 Detailed ChangesLog: #625 Non explicit error while loading a project #758 [Regression] Repair action clone is not setting pharo repository #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of IceTipURLLabelMorph did not understand #addEmphasis:) #749 Adding repair actions to the code subdirectory missing problem #655 Rename extension method buildToolbarItem of CommandActivator #755 Extracting the URL label behavior as a component that we can reuse #468 Commiting via Iceberg does not commit package removal #750 Add possibility to see current commit in Repositories/Package view #754 Showing and coping the Commit ID #753 Create branch dialog layout is broken #664 Package wrongly shown with "uncommited changes" status #752 Add "invalid ssh" #747 Cloning a Git repository should change the path with the project name. #738 Remove "pharo" Repository with "also remove from filesystem" gives error #746 Make tests run on pharo 6 #735 Issue while registering a new project on Pharo 6.1 #733 Add license file #740 Fogbugz panel: Improve label, focus order and layout #549 IceRestoreRepositoryModel should have a class comment #688 Duplicated project error when loading in a fresh image Enjoy, Guille in behalf of all people that contributed :)

3 3