- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #168: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr March 21, 2019

March 21, 2019

There is a new Pharo build available! The status of the build #168 was: FAILURE. Could not extract further issue information from commit message: Update stale.yml lower stale period for issues: one month is enough Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #167: Remove flaky test
by ci-pharo-ci-jenkins2＠inria.fr March 21, 2019

March 21, 2019

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

1 0

About a better filedialog
by ducasse March 21, 2019

March 21, 2019

Hi guys I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. what do you think? https://github.com/Ducasse/file-dialog I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). When Spec2 is out I would like to port it to Spec2. Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. Stef

5 14

[Pharo 8.0] Build #166: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr March 21, 2019

March 21, 2019

There is a new Pharo build available! The status of the build #166 was: FAILURE. Could not extract further issue information from commit message: add config for https://github.com/probot/stale Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #165: 2929-Move-method-comment-parsing-from-Behaviour-to-CompiledMethod
by ci-pharo-ci-jenkins2＠inria.fr March 21, 2019

March 21, 2019

There is a new Pharo build available! The status of the build #165 was: FAILURE. The Pull Request #2930 was integrated: "2929-Move-method-comment-parsing-from-Behaviour-to-CompiledMethod" Pull request url: https://github.com/pharo-project/pharo/pull/2930 Issue Url: https://pharo.fogbugz.com/f/cases/2929 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Why everybody could have an impact?
by ducasse March 20, 2019

March 20, 2019

Hi to relax I was going over RB code because we will start to improve the refactoring. And I started to add tests (yes the dummy little things that everybody can write but that most people prefer to think they do and talk about). And writing such super super stupid tests testCheckInvalidMethodName "Usually used to validate input." self deny: (RBCondition checkMethodName: 'fofo fo'). self deny: (RBCondition checkMethodName: '123fofo'). "self deny: (RBCondition checkMethodName: 'foo::')." "self deny: (RBCondition checkMethodName: 'agr:goo:aa').â checkMethodName: aString "Return whether the argument aName is can represent a selector" ^ aString isString and: [ RBScanner isSelector: aString ] I found that RBScanner reports that #foo:: or 'agr:goo:aaâ is a valid selector :( So if you **really** want to help pharo this is not that difficult. Now this is a matter of will. Stef

2 3

Is String withUnixLineEnding mutation behavior a bug?
by Ronie Salgado March 20, 2019

March 20, 2019

Hi, I just noticed that String >> withUnixLineEndings modifies the the original string, at least when the string only has cr, and not crlf. For example, try the following (in Pharo 7) in a Playground: original :='asa' , String cr , 'asa'. newString := original withUnixLineEndings. original at: 4. Best regards, Ronie

2 1

[Pharo 8.0] Build #164: Integrate Clap
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2019

March 20, 2019

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

1 0

Weird SUnit/TestRunner behavior
by Attila Magyar March 20, 2019

March 20, 2019

Hi, This was originally reported as a BabyMock bug but it looks like it effects normal test cases as well. Let's say I have a test like this: MyTest>>initialize super initialize. s := OrderedCollection new. "note that this is initialized here not in the setUp as we normally do" MyTest>>testWhatever s add: 42. 1 / 0. Open the Test Runner tool, run the test, it'll fail as expected. Now click on the failed test (in the test runner window) and the debugger will popup saying that #add: was sent to nil. Instance variables are cleared out after a test run but initialize is not called before running it again. Is this expected? The same doesn't cause any problems when I run it from the System Browser. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

5 10

[Pharo 8.0] Build #163: 2925-Integrate-latest-version-of-Hiedra
by ci-pharo-ci-jenkins2＠inria.fr March 20, 2019

March 20, 2019

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

1 0