- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Loading configuration of spur

by Guillermo Polito

Hmm no idea. The best I can think about is that that VMMaker version is old (Pharo5 is at least 2 years old) and there is probably a dependency between VMMaker and the compiler (thus that BytecodeEncoder ref). IF VMMaker is overriding some methods in BytecodeEncoder, then what is happenning is that you're breaking the compiler (?). In any case, again, that is not the official VMMaker repository but a mirror. On Mon, Mar 12, 2018 at 11:53 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > Oh I forgot to write down the actual error. There is a MNU for > BytecodeEncoder class>>#isExtension: which seems to have been removed from > the image. It is a bit different to typical doesNotUnderstand errors > because it opens an emergency evaluator and leaves the image unusable. > > On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi, >> >> I'll Esteban answer better but I don't know if that VMMaker mirror is up >> to date. >> >> Taking a look at the images/newImage.sh script, it is using Pharo5.0. But >> I see no reason for it not working on latest versions. Probably some >> patches are required... >> >> What is your error? >> >> >> On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com >> > wrote: >> >>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 >>> image, is that supported? I have this snippet that doesn't work: >>> >>> Metacello new >>> filetreeDirectory: '../VMMaker/mc'; >>> baseline: 'Spur'; >>> load >>> >>> where ../VMMaker/mc is a clone of the official pharo repo at github. >>> >>> Cheers, >>> pocho >>> >>> -- >>> Javier PimÃ¡s >>> Ciudad de Buenos Aires >>> >> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013> >> > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 12, 2018

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

by Juraj Kubelka

Hi! thank you, it works! Juraj > El 27-02-2018, a las 20:19, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> escribiÃ³: > > Le 25/02/2018 Ã 23:07, Cyril Ferlicot D. a Ã©crit : >> Hi! >> >> This support is in this PR: >> >> https://github.com/pharo-project/pharo/pull/950 >> >> It was not added in Pharo 7 during the last sync but was in Pharo 6.1. >> >> I hope in the future we will depend on Metacello as a project during the >> bootstrap instead of having the sources directly in the Pharo >> repository. It will help but it needs work. >> > > > Hi! > > It is integrated. Can you check in the latest Pharo please? > > -- > Cyril Ferlicot > https://ferlicot.fr >

March 12, 2018

Re: [Pharo-dev] Loading configuration of spur

by Javier PimÃ¡s

Oh I forgot to write down the actual error. There is a MNU for BytecodeEncoder class>>#isExtension: which seems to have been removed from the image. It is a bit different to typical doesNotUnderstand errors because it opens an emergency evaluator and leaves the image unusable. On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi, > > I'll Esteban answer better but I don't know if that VMMaker mirror is up > to date. > > Taking a look at the images/newImage.sh script, it is using Pharo5.0. But > I see no reason for it not working on latest versions. Probably some > patches are required... > > What is your error? > > > On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> > wrote: > >> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 >> image, is that supported? I have this snippet that doesn't work: >> >> Metacello new >> filetreeDirectory: '../VMMaker/mc'; >> baseline: 'Spur'; >> load >> >> where ../VMMaker/mc is a clone of the official pharo repo at github. >> >> Cheers, >> pocho >> >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <06%2052%2070%2066%2013> > -- Javier PimÃ¡s Ciudad de Buenos Aires

March 12, 2018

Re: [Pharo-dev] pharo64+git crash

by Esteban Lorenzano

I think I will declare new stables today. this is becoming a too confusing, and latest VMs are working fine, AFAIK ;) Esteban > On 11 Mar 2018, at 19:41, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 11/03/2018 Ã 18:09, Javier PimÃ¡s a Ã©crit : >> Didn't work. Tried also with vmT70 and vmI70 and neither did work. Sometimes they segfault, sometimes they hang using 100% cpu. I noticed that being for pharo7 those vms seemed pretty old (aug-2017), so I tried vmTLatest70 and that one finally worked. > > Oh :( Thank you for pointing that it worked with the latest 70 vm. > > I must admit that I'm using directly downloaded recent vms to avoid that same segfault and not the pharo.org <http://pharo.org/> VMs, but the process for setting them is a bit complex. So I hoped that the problem was solved with the Pharo 7 VMs, which are newer. > > Thierry > >> On Sun, Mar 11, 2018 at 6:31 AM, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com> <mailto:thierry.goubier@gmail.com <mailto:thierry.goubier@gmail.com>>> wrote: >> Hi Javier, >> can you try with a 64 bits Pharo 7 vm >> (http://get.pharo.org/64/vm70 <http://get.pharo.org/64/vm70>)? The Pharo 6 64bits vm used to have >> segfaults upon code loading. >> Regards, >> Thierry >> Le 10/03/2018 Ã 22:59, Javier PimÃ¡s a Ã©crit : >> Hi, I wonder if I'm doing something wrong or using a wrong version: >> I download a pharo image (spur64) from >> http://files.pharo.org/get-files/61/pharo64.zip <http://files.pharo.org/get-files/61/pharo64.zip> >> <http://files.pharo.org/get-files/61/pharo64.zip <http://files.pharo.org/get-files/61/pharo64.zip>> >> and a 64 bit vm from: >> get.pharo.org/64/vm61 <http://get.pharo.org/64/vm61> <http://get.pharo.org/64/vm61 <http://get.pharo.org/64/vm61>> >> <http://get.pharo.org/64/vm61> >> Then I try to load a git repo like this: >> ./pharo Pharo.image ../scripts/loadSqueakNOSVM.st >> where the script just says >> "Based on the same file from the pharo-vm project" >> Author useAuthor: 'LoadVMMaker' during: [ >> Metacello new >> baseline: #Nopsys; >> repository: 'github://nopsys/CogNOS/VM-src'; >> load ]. >> (Smalltalk saveAs: 'generator') >> ifFalse: [ Smalltalk snapshot: false andQuit: true ]. >> and it crashes with the log pasted below. I cannot even load the >> code, any clue? >> Cheers, >> Pocho >> ---- >> Fetched -> BaselineOfNopsys-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Loaded -> BaselineOfNopsys-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Loading baseline of BaselineOfNopsys... >> Fetched -> SqueakNOS-VM-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Fetched -> BaselineOfSpur-EstebanLorenzano.4 --- >> filetree:///CogNOS/VMMaker/mc [:] --- filetree:///CogNOS/VMMaker/mc >> Segmentation fault Sat Mar 10 18:36:05 2018 >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo >> Pharo VM version: 5.0-201707201942 Thu Jul 20 20:40:54 UTC 2017 >> gcc 4.6.3 [Production Spur 64-bit VM] >> Built from: CoInterpreter VMMaker.oscog-eem.2254 uuid: >> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 >> With: StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: >> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 >> Revision: VM: 201707201942 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ Date: >> Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ >> Build host: Linux >> testing-gce-74d10329-bbfd-42e5-8995-b0e3a68c73cb >> 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 >> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux >> plugin path: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942 >> [default: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/] >> C stack backtrace & registers: >> rax 0x0c1c5f40 rbx 0x0c1c5dd0 rcx 0x0c1c5ff8 rdx 0x0c1c5e88 >> rdi 0x0c1c5ba8 rsi 0x0c1c5ba8 rbp 0x0c1c5d18 rsp 0x0c1c60b0 >> r8 0x0c1c55e8 r9 0x0c1c56a0 r10 0x0c1c5758 r11 0x0c1c5810 >> r12 0x0c1c58c8 r13 0x0c1c5980 r14 0x0c1c5a38 r15 0x0c1c5af0 >> rip 0x0c1c6168 >> *[0x7ffd0c1c6168] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41ccd1] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41d05f] >> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11670)[0x7f5dc882f670] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x4403cc] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo(ceSendAborttonumArgs+0xd6)[0x45b826] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x45bda3] >> [0x1501223] >> [0x7ffdffffffff] >> Smalltalk stack dump: >> 0x7ffd0c1cbcc0 M MCWorkingCopy >> class>ancestorsFromArray:cache: 0x2b4a8a0: a(n) MCWorkingCopy class >> 0x19abee8 is not a context >> 0x1a24a80 is not a context >> 0x19abd78 is not a context >> 0x1a2c118 is not a context >> ... >> -- Javier PimÃ¡s >> Ciudad de Buenos Aires >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires

March 12, 2018

Re: [Pharo-dev] Loading configuration of spur

by Guillermo Polito

Hi, I'll Esteban answer better but I don't know if that VMMaker mirror is up to date. Taking a look at the images/newImage.sh script, it is using Pharo5.0. But I see no reason for it not working on latest versions. Probably some patches are required... What is your error? On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 > image, is that supported? I have this snippet that doesn't work: > > Metacello new > filetreeDirectory: '../VMMaker/mc'; > baseline: 'Spur'; > load > > where ../VMMaker/mc is a clone of the official pharo repo at github. > > Cheers, > pocho > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 12, 2018

Pharo VM crash in bootstrap with Inconsistency detected by ld.so

by Alistair Grant

Hi Tobias, Esteban and Fabio, Attempting to bootstrap the image with Pharo 7.0 VMs newer than 30 Jan are failing with: + vm/pharo Pharo7.0-32bit-eabf524.image eval --save "Metacello new baseline: 'Tonel';repository: 'github://pharo-vcs/tonel:v1.0.5';onWarning: [ :e | Error signal: e messageText in: e signalerContext ]; load: 'core'" ... ...finished baselinelinear load : linear load : baseline [BaselineOfTonel] load : MonticelloTonel-Core-cypress.1 load : MonticelloTonel-FileSystem-cypress.1 Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion `map->l_init_called' failed! VMs prior to this succeed (e.g. the current stable vm70). The error is happening after the image is saved, so it is actually possible to continue and successfully bootstrap the image, but obviously that is not solving the core issue. Building a debug VM gives more information: $ gdb ../vmtarget/lib/pharo/5.0-201803091840-21462-Open-a-FileStream-based-on-fd-or-FILE/pharo GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ../vmtarget/lib/pharo/5.0-201803091840-21462-Open-a-FileStream-based-on-fd-or-FILE/pharo...done. (gdb) run --headless Pharo7.0-32bit-eabf524.image eval --save "Metacello new baseline: 'Tonel';repository: 'github://pharo-vcs/tonel:v1.0.5';onWarning: [ :e | Error signal: e messageText in: e signalerContext ]; load: 'core'" Starting program: /home/alistair/pharo7/bootstrap/pharo/vmtarget/lib/pharo/5.0-201803091840-21462-Open-a-FileStream-based-on-fd-or-FILE/pharo --headless Pharo7.0-32bit-eabf524.image eval --save "Metacello new baseline: 'Tonel';repository: 'github://pharo-vcs/tonel:v1.0.5';onWarning: [ :e | Error signal: e messageText in: e signalerContext ]; load: 'core'" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0xf7a7cb40 (LWP 27000)] Loading (null) Loading libssl.so Found libssl.so at libssl.so.1.0.0 Found symbol ASN1_STRING_data in dlhandle_ssl Found symbol ASN1_STRING_length in RTLD_DEFAULT Found symbol BIO_free_all in RTLD_DEFAULT Found symbol BIO_new in RTLD_DEFAULT Found symbol BIO_s_mem in RTLD_DEFAULT Found symbol BIO_ctrl_pending in RTLD_DEFAULT Found symbol BIO_ctrl in RTLD_DEFAULT Found symbol BIO_write in RTLD_DEFAULT Found symbol BIO_read in RTLD_DEFAULT Found symbol ERR_print_errors_fp in RTLD_DEFAULT Found symbol SSL_CTX_free in RTLD_DEFAULT Found symbol SSL_CTX_set_cipher_list in RTLD_DEFAULT Found symbol SSL_CTX_set_default_verify_paths in RTLD_DEFAULT Found symbol SSL_CTX_ctrl in RTLD_DEFAULT Found symbol SSL_CTX_use_PrivateKey_file in RTLD_DEFAULT Found symbol SSL_CTX_use_certificate_file in RTLD_DEFAULT Found symbol SSL_accept in RTLD_DEFAULT Found symbol SSL_connect in RTLD_DEFAULT Found symbol SSL_free in RTLD_DEFAULT Found symbol SSL_ctrl in RTLD_DEFAULT Found symbol SSL_get_error in RTLD_DEFAULT Found symbol SSL_get_peer_certificate in RTLD_DEFAULT Found symbol SSL_get_verify_result in RTLD_DEFAULT Found symbol SSL_new in RTLD_DEFAULT Found symbol SSL_read in RTLD_DEFAULT Found symbol SSL_set_accept_state in RTLD_DEFAULT Found symbol SSL_set_bio in RTLD_DEFAULT Found symbol SSL_set_connect_state in RTLD_DEFAULT Found symbol SSL_write in RTLD_DEFAULT Found symbol X509_NAME_get_text_by_NID in RTLD_DEFAULT Found symbol X509_get_subject_name in RTLD_DEFAULT Found symbol X509_get_ext_d2i in RTLD_DEFAULT Found symbol X509_free in RTLD_DEFAULT Found symbol X509_check_ip_asc in RTLD_DEFAULT Found symbol X509_check_host in RTLD_DEFAULT Loading libcrypto.so Found libcrypto.so at libcrypto.so.1.0.0 Cannot find SSL_CTX_set_options Found symbol BIO_test_flags in RTLD_DEFAULT Cannot find ASN1_STRING_get0_data Found symbol sk_new_null in RTLD_DEFAULT Found symbol sk_push in RTLD_DEFAULT Found symbol sk_free in RTLD_DEFAULT Found symbol sk_value in RTLD_DEFAULT Found symbol sk_num in RTLD_DEFAULT Found symbol sk_pop_free in RTLD_DEFAULT Found symbol SSLv23_method in RTLD_DEFAULT Found symbol SSL_CTX_new in RTLD_DEFAULT Cannot find OPENSSL_sk_new_null Cannot find OPENSSL_sk_push Cannot find OPENSSL_sk_free Cannot find OPENSSL_sk_value Cannot find OPENSSL_sk_num Cannot find OPENSSL_sk_pop_free Cannot find TLS_method Found symbol SSL_library_init in RTLD_DEFAULT Found symbol SSL_load_error_strings in RTLD_DEFAULT Cannot find OPENSSL_init_ssl Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- github://pharo-vcs/tonel:v1.0.5 Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- github://pharo-vcs/tonel:v1.0.5 Loading baseline of BaselineOfTonel... Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- github://pharo-vcs/tonel:v1.0.5 Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- github://pharo-vcs/tonel:v1.0.5 Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- cache Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:v1.0.5 --- cache ...finished baselinelinear load : linear load : baseline [BaselineOfTonel] load : MonticelloTonel-Core-cypress.1 load : MonticelloTonel-FileSystem-cypress.1 Inconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion `map->l_init_called' failed! [Thread 0xf7a7cb40 (LWP 27000) exited] [Inferior 1 (process 26996) exited with code 0177] (gdb) The problem occurrs some time between: VM 30 Jan 2018 14:55 commit 0d66d2a (bootstrap succeeds) and: VM 31 Jan 2018 14:13 commit 0456605 (bootstrap fails) These are two consecutive VMs on files.pharo.org, so I can't check commits in between by downloading, and my attempts to build the VMs failed. The commit messages are: commit 045660598ed0a743d9430b600f3b2ac9cf31d4c4 Merge: b251d57 74e443c Author: Fabio Niephaus <code(a)fniephaus.com> Date: Wed Jan 31 15:13:15 2018 +0100 Merge pull request #205 from OpenSmalltalk/dl-openssl [SqueakSSL] Overlay OpenSSL for linux/unix commit 74e443c1e2c1492ee7677471730182393f5ae996 Author: Fabio Niephaus <code(a)fniephaus.com> Date: Wed Jan 31 14:35:45 2018 +0100 Nit picks [ci skip] commit 438311cb201cfc01dcb03ddcf034cfb5176b57f4 Author: Tobias Pape <tobias(a)netshed.de> Date: Wed Jan 31 14:27:31 2018 +0100 Refactor the overlay, comments where due commit b251d57fec7da2f19945c0555b3847f1e397cd71 Merge: 0d66d2a 66d5790 Author: Fabio Niephaus <code(a)fniephaus.com> Date: Wed Jan 31 10:50:39 2018 +0100 Merge pull request #206 from estebanlm/add-pharo-certificates new try with certificates commit 66d579096b9d954ed208b621770a937639f58031 Author: Esteban Lorenzano <estebanlm(a)gmail.com> Date: Wed Jan 31 09:33:11 2018 +0100 new try commit 8e48e6f2a94ecac2010550b68c2ceab6cf7cde91 Author: Tobias Pape <tobias(a)netshed.de> Date: Tue Jan 30 21:15:51 2018 +0100 Allow for possibly undefined X509 constant commit 49353ed2783531b3c8fcb7a522dc6f578ea5414c Author: Tobias Pape <tobias(a)netshed.de> Date: Tue Jan 30 20:09:38 2018 +0100 [SqueakSSL] Overlay OpenSSL for linux/unix When we dynamically link against OpenSSL, the bundles are not portable, as CentOS and friends use other SO_NAMEs than Debian and friends. Also, soft-fallback for later features such as host name verification is hard. When we statically link, we might lack behind the OS, the binaries are bigger, and the legal situation is less clear. So we now support not linking at all but rather lookup all necessary functions/symbols at runtime. This can be disabled with SQSSL_OPENSSL_LINKED which effectively results in the dynamically-linked behavior. (This is preferable for platform builds, eg, debs and rpms) I'm struggling to figure this one out at the moment and am hoping that one of you might recognise something to help track it down... P.S. I also tried compiling with -DSQSSL_OPENSSL_LINKED, but that produced compiler errors. Help :-) Alistair

March 12, 2018

[Pharo 7.0-dev] Build #689: 21563 Two small cleanups in InstructionStream

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

There is a new Pharo build available! The status of the build #689 was: SUCCESS. The Pull Request #1088 was integrated: "21563 Two small cleanups in InstructionStream" Pull request url: https://github.com/pharo-project/pharo/pull/1088 Issue Url: https://pharo.fogbugz.com/f/cases/21563 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 12, 2018

Esteban's ChangeLog week of 5 March 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 5 March 2018 to 11 March 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/3/2018&to=11/3/2018 ChangeLog ========= 5 March 2018: ------------- * Today I worked on details of Pull/Push views, and I fixed some pending issues with all the others. As a side note, I added badges to my toolbars ;) Is not finished yet (I guess it will be tomorrow), but is a good way to present certain information. cheers! Esteban

March 12, 2018

[Pharo 7.0-dev] Build #688: 21564 TraitBuilderEnhancer should use utilities protocol

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

There is a new Pharo build available! The status of the build #688 was: SUCCESS. The Pull Request #1089 was integrated: "21564 TraitBuilderEnhancer should use utilities protocol" Pull request url: https://github.com/pharo-project/pharo/pull/1089 Issue Url: https://pharo.fogbugz.com/f/cases/21564 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 12, 2018

[Pharo 7.0-dev] Build #687: 21551 Cleanup testCompositionCopy

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

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

March 11, 2018