[Pharo-dev] [Pharo 8.0] Build #1128: fixing ring version in PharoBootstrapProcess
There is a new Pharo build available! The status of the build #1128 was: SUCCESS. The Pull Request #5647 was integrated: "fixing ring version in PharoBootstrapProcess" Pull request url: https://github.com/pharo-project/pharo/pull/5647 Issue Url: https://github.com/pharo-project/pharo/issues/fix Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/1128/
[Pharo-dev] [FOSDEM] Grafoscopio
Fosdem organization uploaded the videos on grafoscopio :). Maybe it would be nice to spread it through our medias https://video.fosdem.org/2020/AW1.126/open_research_pocket_infrastructures.mp4 https://video.fosdem.org/2020/AW1.126/open_research_pocket_infrastructures.webm Santiago
[Pharo-dev] Bug 18632 : Virtual Machine parameters need to be documented
--- Begin Message --- I was looking for some documentation on VM parameters (are they read, read-write or write only as well as the expected argument type) and came across that issue on the old FogBugz database. https://pharo.fogbugz.com/f/cases/18632/Virtual-Machine-parameters-need-to-be-documented I tried looking it up on GitHub but couldn't find it. Am I missing something or I should open an issue? I'm working on something related to various memory settings and not having any info on a lot of these parameters doesn't help. While I could meticulously read tons of C code of the VM and pinpoint exactly what I need to know for each and everyone of these undocumented parameters, I'd gladly do it myself if any of the VM guys (Clément, Pablo, Alexandre or Eliot) have notes/documents/links that could help me do it. tia -- - Benoît St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth GitHub: bstjean Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein) --- End Message ---
Re: [Pharo-dev] PR without Tests
--- Begin Message --- Great news! I was wondering if they were also something planned to get some coverage information report to help to add more tests on parts of the system that are not tested? Cheers, Vincent -Original Message- From: Pharo-dev On Behalf Of teso...@gmail.com Sent: Thursday, 6 February 2020 10:30 To: Pharo-dev ; r...@inria.fr list Subject: [Pharo-dev] PR without Tests Hello, Pharo is not Smalltalk / Smalltalk is not Pharo / Pharo is Smalltalk. Now that I have your attention because it seems the only read mail has to have this. We have to continue improving the quality of Pharo. One of the biggest assets that we have in Pharo are the tons of tests. So, we need to reject any PR that does not have tests or it is not already tested. To ease this quality measure, please add some comments on the PR about how your new code or modified code is tested or benchmarked. Cheers. -- Pablo Tesone. teso...@gmail.com --- End Message ---
Re: [Pharo-dev] [rmod] PR without Tests
+1000 > On 6 Feb 2020, at 10:29, teso...@gmail.com wrote: > > > --
Re: [Pharo-dev] PR without Tests
Of course, the already open PR are there, and it is ok, we can handle them. On Thu, Feb 6, 2020 at 10:29 AM teso...@gmail.com wrote: > > Hello, >Pharo is not Smalltalk / Smalltalk is not Pharo / Pharo is Smalltalk. > Now that I have your attention because it seems the only read mail has > to have this. > > We have to continue improving the quality of Pharo. One of the biggest > assets that we have in Pharo are the tons of tests. So, we need to > reject any PR that does not have tests or it is not already tested. > > To ease this quality measure, please add some comments on the PR about > how your new code or modified code is tested or benchmarked. > > Cheers. > > -- > Pablo Tesone. > teso...@gmail.com -- Pablo Tesone. teso...@gmail.com
[Pharo-dev] PR without Tests
Hello, Pharo is not Smalltalk / Smalltalk is not Pharo / Pharo is Smalltalk. Now that I have your attention because it seems the only read mail has to have this. We have to continue improving the quality of Pharo. One of the biggest assets that we have in Pharo are the tons of tests. So, we need to reject any PR that does not have tests or it is not already tested. To ease this quality measure, please add some comments on the PR about how your new code or modified code is tested or benchmarked. Cheers. -- Pablo Tesone. teso...@gmail.com
