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

[Pharo 7.0] Build #44: 22772-chooseExistingFileReferenceextensionspathpreview-returning-wrong-FileReference

by ci-pharo-ci-jenkins2＠inria.fr

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

Dec. 14, 2018

Re: [Pharo-dev] Pharo image don't restart

by Trussardi Dario Romano

>> ...........r3732#linux >> Errore di segmentazione (core dump creato) >> >> C) i have a PharoDebug.log but has the size of 16MB. >> >> How can I send it to you? > > you can try something like https://wetransfer.com can you download the PharoDebug.log from link into my previous email? The PharoDebug.log. You can view it? Dario ................................................ Questo messaggio contiene i seguenti allegati: PharoDebug.log[15.24 MB] Dimensioni totali dei file inviati:15.24 MB Ciao, Dario

Dec. 14, 2018

[Pharo 7.0] Build #43: 22744 Package manifest ManifestFuel should be tagged and commented

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #43 was: FAILURE. The Pull Request #2052 was integrated: "22744 Package manifest ManifestFuel should be tagged and commented" Pull request url: https://github.com/pharo-project/pharo/pull/2052 Issue Url: https://pharo.fogbugz.com/f/cases/22744 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2018

[Pharo 7.0] Build #42: 22754-Exception-while-opening-a-MCSubDirectoryRepository

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #42 was: SUCCESS. The Pull Request #2062 was integrated: "22754-Exception-while-opening-a-MCSubDirectoryRepository" Pull request url: https://github.com/pharo-project/pharo/pull/2062 Issue Url: https://pharo.fogbugz.com/f/cases/22754 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2018

Re: [Pharo-dev] Pharo image don't restart

by Christophe Demarey

> Le 14 dÃ©c. 2018 Ã 12:41, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> a Ã©crit : > > Some consideration: > > > At 12 December: > > I work all day with the image. > > at: 19:xx I save the image without any problem. > > But after saved the image the system begin unstable. > > When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image crash. > > Some time i can launch - relaunch the same image from the PharoLauncher ( the pharo run but was unstable ) > > at: 19:45 After reload the unstable image ( as mentioned above ) > > i do the save command ( saving it on itself ) and the system crash. > > After this crash ( when i do the image save command ), > > i have not been able to launch the image. > > I do not know the status of this image ( I call this corrupt image ) > > > At 13 December: > > A) From pharoLauncher i launch the corrupt image some time, > > the shell report the issue, > > <errorePharo.txt> > > but don't create the crash.dmp file. > > > > B) After copy the pharoLauncher corrupt image into Pharo7.0-64DTRDevErr entry > > i do this: > > /opt/pharolauncher/pharo-vm$ ./pharo --eden 15207744 /home/party/Pharo/images/Pharo7.0-64DTRDevErr/Pharo7.0-64DTRDevErr.image > > the shell report: > > pthread_setschedparam failed: Operation not permitted > This VM uses a separate heartbeat thread to update its internal clock > and handle events. For best operation, this thread should run at a > higher priority, however the VM was unable to change the priority. The > effect is that heavily loaded systems may experience some latency > issues. If this occurs, please create the appropriate configuration > file in /etc/security/limits.d/ as shown below: > > cat <<END | sudo tee /etc/security/limits.d/pharo.conf > * hard rtprio 2 > * soft rtprio 2 > END > > and report to the pharo mailing list whether this improves behaviour. > > You will need to log out and log back in for the limits to take effect. > For more information please see > ...........r3732#linux > Errore di segmentazione (core dump creato) > > C) i have a PharoDebug.log but has the size of 16MB. > > How can I send it to you? you can try something like https://wetransfer.com

Dec. 14, 2018

Re: [Pharo-dev] Pharo image don't restart

by Trussardi Dario Romano

Some consideration: At 12 December: I work all day with the image. at: 19:xx I save the image without any problem. But after saved the image the system begin unstable. When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image crash. Some time i can launch - relaunch the same image from the PharoLauncher ( the pharo run but was unstable ) at: 19:45 After reload the unstable image ( as mentioned above ) i do the save command ( saving it on itself ) and the system crash. After this crash ( when i do the image save command ), i have not been able to launch the image. I do not know the status of this image ( I call this corrupt image ) At 13 December: A) From pharoLauncher i launch the corrupt image some time, the shell report the issue, but don't create the crash.dmp file. B) After copy the pharoLauncher corrupt image into Pharo7.0-64DTRDevErr entry i do this: /opt/pharolauncher/pharo-vm$ ./pharo --eden 15207744 /home/party/Pharo/images/Pharo7.0-64DTRDevErr/Pharo7.0-64DTRDevErr.image the shell report: pthread_setschedparam failed: Operation not permitted This VM uses a separate heartbeat thread to update its internal clock and handle events. For best operation, this thread should run at a higher priority, however the VM was unable to change the priority. The effect is that heavily loaded systems may experience some latency issues. If this occurs, please create the appropriate configuration file in /etc/security/limits.d/ as shown below: cat <<END | sudo tee /etc/security/limits.d/pharo.conf * hard rtprio 2 * soft rtprio 2 END and report to the pharo mailing list whether this improves behaviour. You will need to log out and log back in for the limits to take effect. For more information please see ...........r3732#linux Errore di segmentazione (core dump creato) C) i have a PharoDebug.log but has the size of 16MB. How can I send it to you? This is the status of the problematic. Thanks, Dario

Dec. 14, 2018

[Pharo 7.0] Build #41: 22764 Cleanup EmbeddedFreeType-Tests and EmbeddedFreeType

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #41 was: SUCCESS. The Pull Request #2068 was integrated: "22764 Cleanup EmbeddedFreeType-Tests and EmbeddedFreeType" Pull request url: https://github.com/pharo-project/pharo/pull/2068 Issue Url: https://pharo.fogbugz.com/f/cases/22764 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2018

Re: [Pharo-dev] Pharo image don't restart

by dario.trussardi＠tiscali.it

The PharoDebug.log. You can view it? Dario ................................................ Questo messaggio contiene i seguenti allegati: PharoDebug.log[15.24 MB] Dimensioni totali dei file inviati:15.24 MB Per scaricarli fai click sul link seguente: http://mail.tiscali.it/bigattachments/?c=dab58fa12765311a72d7a919d118e2b1 Allega Maxi Ã¨ il servizio di Tiscali WebMail che permette di allegare file, fino a 2GB, senza problemi di superamento dei limiti delle normali caselle e-mail. Ti ricordiamo che questo link sara' valido fino al giorno 17/12/2018 ................................................ Con OpenStar hai Giga, SMS e i minuti che vuoi da 4,99â¬ al mese, per sempre. Cambi gratis quando e come vuoi e in piÃ¹ hai 10â¬ di credito omaggio e 6 mesi di INFINTY! http://tisca.li/myopen

Dec. 14, 2018

[Pharo 7.0] Build #40: 22769-KeyboardKey-classunixVirtualKeyTable-uses-KeyTable-instead-of-UnixKeyTable-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #40 was: FAILURE. The Pull Request #2074 was integrated: "22769-KeyboardKey-classunixVirtualKeyTable-uses-KeyTable-instead-of-UnixKeyTable-" Pull request url: https://github.com/pharo-project/pharo/pull/2074 Issue Url: https://pharo.fogbugz.com/f/cases/22769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2018

[Pharo 7.0] Build #39: 22728-Add-enough-informations-to-Metacello-to-load-a-project-from-a-gitlab-deployed-with-non-default-ssh-port

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #39 was: SUCCESS. The Pull Request #2041 was integrated: "22728-Add-enough-informations-to-Metacello-to-load-a-project-from-a-gitlab-deployed-with-non-default-ssh-port" Pull request url: https://github.com/pharo-project/pharo/pull/2041 Issue Url: https://pharo.fogbugz.com/f/cases/22728 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 14, 2018