February 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #560: 21358-Renraku-evaluator-creates-the-AST-of-the-methods-even-if-they-are-not-used-at-all
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #560 was: SUCCESS. The Pull Request #901 was integrated: "21358-Renraku-evaluator-creates-the-AST-of-the-methods-even-if-they-are-not-used-at-all" Pull request url: https://github.com/pharo-project/pharo/pull/901 Issue Url: https://pharo.fogbugz.com/f/cases/21358 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #553: 20941-deprecate-theMetaclass-and-the-theNonMeta
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

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

5 8

[Pharo 7.0-dev] Build #559: 21360-Kernel-Tests-Methods-CompiledMethodTest-testSelector-produces-a-DNU
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #559 was: FAILURE. The Pull Request #903 was integrated: "21360-Kernel-Tests-Methods-CompiledMethodTest-testSelector-produces-a-DNU" Pull request url: https://github.com/pharo-project/pharo/pull/903 Issue Url: https://pharo.fogbugz.com/f/cases/21360 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #558: 21356-MetaLink-add-Inspector-tab-showing-definition-
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #558 was: FAILURE. The Pull Request #900 was integrated: "21356-MetaLink-add-Inspector-tab-showing-definition-" Pull request url: https://github.com/pharo-project/pharo/pull/900 Issue Url: https://pharo.fogbugz.com/f/cases/21356 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #557: 21354 Cleanup UnicodeTest (lint)
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

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

2 1

Random corrupted data when copying from very large byte array
by Cyrille Delaunay Feb. 16, 2018

Feb. 16, 2018

Hi everyone, I just added a new bug entry for an issue we are experimenting since some times: https://pharo.fogbugz.com/f/cases/20982/Random-corrupted-data-when-copying-… Here is the description: *History:* This issue has been spotted after experimenting strange behavior with seaside upload. After uploading a big file from a web browser, the modeled file generated within pharo image begins with 4 unexpected bytes. This issue occurs randomly: sometimes the first 4 bytes are right. Sometimes the first 4 bytes are wrong. This issue only occurs with Pharo 6. This issue occurs for all platforms (Mac, Ubuntu, Windows) *Steps to reproduce:* I have been able to set up a small scenario that highlight the issue. Download Pharo 6.1 on my Mac (Sierra 10.12.6): https://pharo.org/web/download Then, iterate over this process till spotting the issue: => start the pharo image => execute this piece of code in a playground 1: 2: 3: 4: 5: 6: ZnServer startDefaultOn: 1701.ZnServer default maximumEntitySize: 80* 1024 * 1024.'/Users/cdelaunay/myzip.zip' asFileReference writeStreamDo: [ :out |out binary; nextPutAll: #[80 75 3 4 10 0 0 0 0 0 125 83 67 73 0 0 0 0 0 0].18202065 timesRepeat: [ out nextPut: 0 ]]. => Open a web browser page on: http://localhost:1701/form-test-3 => Upload the file zip file previously generated ('myzip.zip'). => If the web page displays: "contents=000000000a00 <https://pharo.kilnhg.com/Search?search=000000000a00>..." (or anything unexpected), THIS IS THE ISSUE ! => If the web page displays: "contents=504b03040a00 <https://pharo.kilnhg.com/Search?search=504b03040a00>..", the upload worked fine. You can close the image (without saving) *Debugging:* Bob Arning has been able to reproduce the issue with my scenario. He dived into the code involved during this process, till reaching some "basic" methods where he saw the issue occuring. Here are the conclusion till there: => A corruption occurs while reading an input stream with method ZnUtils class>>readUpToEnd:limit: The first 4 bytes may be altered randomely. => The first 4 bytes are initially correctly written to an outputStream. But, the first 4 bytes of this outputStream gets altered (corrupted), sometimes when the inner byte array grows OR when performing the final "outputStream contents" => Here is a piece of code that reproduce the issue (still randomely. stopping an restarting the image may change the behavior) 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: test4"self test4" | species bufferSize buffer totalRead outputStream answer inputStream ba byte1 | ba := ByteArray new: 18202085. ba atAllPut: 99. 1 to: 20 do: [ :i | ba at: i put: (#[80 75 3 4 10 7 7 7 7 7 125 83 67 73 7 7 7 7 7 7] at: i) ]. inputStream := ba readStream. bufferSize := 16384. species := ByteArray. buffer := species new: bufferSize. totalRead := 0. outputStream := nil. [ inputStream atEnd ] whileFalse: [ | readCount | readCount := inputStream readInto: buffer startingAt: 1 count: bufferSize. totalRead = 0 ifTrue: [ byte1 := buffer first. ]. totalRead := totalRead + readCount. outputStream ifNil: [ inputStream atEnd ifTrue: [ ^ buffer copyFrom: 1 to: readCount ] ifFalse: [ outputStream := (species new: bufferSize) writeStream ] ]. outputStream next: readCount putAll: buffer startingAt: 1. byte1 = outputStream contents first ifFalse: [ self halt ]. ]. answer := outputStream ifNil: [ species new ] ifNotNil: [ outputStream contents ]. byte1 = answer first ifFalse: [ self halt ]. ^answer *suspicions* This issue appeared with Pharo 6. Some people suggested that it could be a vm issue, and to try my little scenario with the last available vm. I am not sure where to find the last available vm. I did the test using these elements: https://files.pharo.org/image/60/latest.zip https://files.pharo.org/get-files/70/pharo-mac-latest.zip/ <https://files.pharo.org/get-files/70/> The issue is still present -- Cyrille Delaunay

6 15

[Pharo 7.0-dev] Build #556: 21353 Cleanup assertions in CompiledMethodTest (testCopy and testCopyWithTrailerBytes)
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #556 was: FAILURE. The Pull Request #896 was integrated: "21353 Cleanup assertions in CompiledMethodTest (testCopy and testCopyWithTrailerBytes)" Pull request url: https://github.com/pharo-project/pharo/pull/896 Issue Url: https://pharo.fogbugz.com/f/cases/21353 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #555: 21351 Remove unnecessary "self run:" in BagTest (last remaining)
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #555 was: SUCCESS. The Pull Request #895 was integrated: "21351 Remove unnecessary "self run:" in BagTest (last remaining)" Pull request url: https://github.com/pharo-project/pharo/pull/895 Issue Url: https://pharo.fogbugz.com/f/cases/21351 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo7 ci] reduced # executors
by Marcus Denker Feb. 16, 2018

Feb. 16, 2018

Hi, For Pharo Builds (Both CI Pull Request checks as well as builds after merges) things will be a bit slow as I reduces for all slaves the number of executors from 4 to 1. Reason: Experiment to see if this leads to more stable performance / less problems Marcus

1 0

[Pharo 7.0-dev] Build #554: 21352 FFICompilerPluginTests setUp needs to call super setUp
by ci-pharo-ci-jenkins2＠inria.fr Feb. 16, 2018

Feb. 16, 2018

There is a new Pharo build available! The status of the build #554 was: SUCCESS. The Pull Request #894 was integrated: "21352 FFICompilerPluginTests setUp needs to call super setUp" Pull request url: https://github.com/pharo-project/pharo/pull/894 Issue Url: https://pharo.fogbugz.com/f/cases/21352 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0