May 2014 - Pharo-dev - lists.pharo.org

Build failed in Jenkins: Pharo-2.0 #364

by no-reply＠ci.inria.fr

See <https://ci.inria.fr/pharo/job/Pharo-2.0/364/> ------------------------------------------ Started by upstream project "Pharo-2.0-Update-Step-0-GitTracker" build number 260 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on rmod-mac302.lille.inria.fr in workspace <https://ci.inria.fr/pharo/job/Pharo-2.0/ws/> Deleting project workspace... done Copied 20 artifacts from "Scripts-download" build number 2301 [Pharo-2.0] $ /bin/sh -xe /var/folders/k0/ljj6f35s7fv8sd6byqvgm9y40000gs/T/hudson4544250141849062083.sh + wget --quiet -O - http://get.pharo.org/20+vm + bash Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/mac/stable.zip pharo-vm/Pharo.app/Contents/MacOS/Pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Downloading PharoV30.sources: http://files.pharo.org/sources//PharoV30.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image update [31m[33m =============================================================================== Notice: 0 new update file(s) processed. =============================================================================== [0m[0m+ zip Pharo.zip Pharo.image Pharo.changes adding: Pharo.image (deflated 58%) adding: Pharo.changes (deflated 89%) + ./pharo Pharo.image printVersion [version] 2.0 #20628 ++ ./pharo Pharo.image printVersion ++ grep --only-matching '[0-9]\{5\}' + VERSION=20628 + ./pharo Pharo.image save Pharo-20628 + zip 20628.zip Pharo-20628.image Pharo-20628.changes adding: Pharo-20628.image (deflated 58%) adding: Pharo-20628.changes (deflated 89%) + cp 20628.zip latest.zip + cp 20628.zip Pharo-Image-2.0-latest.zip + mkdir One + cp Pharo.image Pharo.changes pharo-vm/PharoV20.sources One + bash build-oneclick.sh -i One/Pharo -o Pharo2.0-portable -v 2.0 -t Pharo chmod: illegal option -- - usage: chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a [i][# [ n]]] mode|entry file ... chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ... chmod: illegal option -- - usage: chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a [i][# [ n]]] mode|entry file ... chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ... chmod: illegal option -- - usage: chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a [i][# [ n]]] mode|entry file ... chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ... chmod: illegal option -- - usage: chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a [i][# [ n]]] mode|entry file ... chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ... chmod: illegal option -- - usage: chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a [i][# [ n]]] mode|entry file ... chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ... --2014-05-06 13:21:00-- http://files.pharo.org/vm/pharo/linux/Pharo-VM-linux-stable.zip Resolving files.pharo.org... 128.93.162.72 Connecting to files.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 744462 (727K) [application/zip] Saving to: âPharo-VM-linux-stable.zipâ 0K .......... .......... .......... .......... .......... 6% 4.01M 0s 50K .......... .......... .......... .......... .......... 13% 7.82M 0s 100K .......... .......... .......... .......... .......... 20% 7.90M 0s 150K .......... .......... .......... .......... .......... 27% 7.77M 0s 200K .......... .......... .......... .......... .......... 34% 75.7M 0s 250K .......... .......... .......... .......... .......... 41% 9.23M 0s 300K .......... .......... .......... .......... .......... 48% 82.5M 0s 350K .......... .......... .......... .......... .......... 55% 9.44M 0s 400K .......... .......... .......... .......... .......... 61% 83.9M 0s 450K .......... .......... .......... .......... .......... 68% 9.69M 0s 500K .......... .......... .......... .......... .......... 75% 57.8M 0s 550K .......... .......... .......... .......... .......... 82% 99.6M 0s 600K .......... .......... .......... .......... .......... 89% 9.25M 0s 650K .......... .......... .......... .......... .......... 96% 87.3M 0s 700K .......... .......... ....... 100% 175M=0.06s 2014-05-06 13:21:00 (12.8 MB/s) - âPharo-VM-linux-stable.zipâ saved [744462/744462] --2014-05-06 13:21:00-- http://files.pharo.org/vm/pharo/mac/Pharo-VM-mac-stable.zip Resolving files.pharo.org... 128.93.162.72 Connecting to files.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2562606 (2.4M) [application/zip] Saving to: âPharo-VM-mac-stable.zipâ 0K .......... .......... .......... .......... .......... 1% 4.04M 1s 50K .......... .......... .......... .......... .......... 3% 4.34M 1s 100K .......... .......... .......... .......... .......... 5% 105M 0s 150K .......... .......... .......... .......... .......... 7% 8.42M 0s 200K .......... .......... .......... .......... .......... 9% 48.0M 0s 250K .......... .......... .......... .......... .......... 11% 9.28M 0s 300K .......... .......... .......... .......... .......... 13% 99.4M 0s 350K .......... .......... .......... .......... .......... 15% 9.05M 0s 400K .......... .......... .......... .......... .......... 17% 83.2M 0s 450K .......... .......... .......... .......... .......... 19% 8.87M 0s 500K .......... .......... .......... .......... .......... 21% 74.4M 0s 550K .......... .......... .......... .......... .......... 23% 108M 0s 600K .......... .......... .......... .......... .......... 25% 9.76M 0s 650K .......... .......... .......... .......... .......... 27% 79.8M 0s 700K .......... .......... .......... .......... .......... 29% 9.72M 0s 750K .......... .......... .......... .......... .......... 31% 58.8M 0s 800K .......... .......... .......... .......... .......... 33% 84.3M 0s 850K .......... .......... .......... .......... .......... 35% 9.85M 0s 900K .......... .......... .......... .......... .......... 37% 134M 0s 950K .......... .......... .......... .......... .......... 39% 9.55M 0s 1000K .......... .......... .......... .......... .......... 41% 70.5M 0s 1050K .......... .......... .......... .......... .......... 43% 85.2M 0s 1100K .......... .......... .......... .......... .......... 45% 8.73M 0s 1150K .......... .......... .......... .......... .......... 47% 115M 0s 1200K .......... .......... .......... .......... .......... 49% 10.4M 0s 1250K .......... .......... .......... .......... .......... 51% 100M 0s 1300K .......... .......... .......... .......... .......... 53% 78.3M 0s 1350K .......... .......... .......... .......... .......... 55% 63.0M 0s 1400K .......... .......... .......... .......... .......... 57% 9.96M 0s 1450K .......... .......... .......... .......... .......... 59% 65.2M 0s 1500K .......... .......... .......... .......... .......... 61% 171M 0s 1550K .......... .......... .......... .......... .......... 63% 182M 0s 1600K .......... .......... .......... .......... .......... 65% 8.73M 0s 1650K .......... .......... .......... .......... .......... 67% 149M 0s 1700K .......... .......... .......... .......... .......... 69% 137M 0s 1750K .......... .......... .......... .......... .......... 71% 130M 0s 1800K .......... .......... .......... .......... .......... 73% 10.4M 0s 1850K .......... .......... .......... .......... .......... 75% 69.0M 0s 1900K .......... .......... .......... .......... .......... 77% 96.3M 0s 1950K .......... .......... .......... .......... .......... 79% 86.0M 0s 2000K .......... .......... .......... .......... .......... 81% 13.1M 0s 2050K .......... .......... .......... .......... .......... 83% 47.8M 0s 2100K .......... .......... .......... .......... .......... 85% 76.7M 0s 2150K .......... .......... .......... .......... .......... 87% 12.2M 0s 2200K .......... .......... .......... .......... .......... 89% 52.3M 0s 2250K .......... .......... .......... .......... .......... 91% 126M 0s 2300K .......... .......... .......... .......... .......... 93% 78.0M 0s 2350K .......... .......... .......... .......... .......... 95% 11.8M 0s 2400K .......... .......... .......... .......... .......... 97% 153M 0s 2450K .......... .......... .......... .......... .......... 99% 121M 0s 2500K .. 100% 50.9K=0.1s 2014-05-06 13:21:00 (20.2 MB/s) - âPharo-VM-mac-stable.zipâ saved [2562606/2562606] --2014-05-06 13:21:01-- http://files.pharo.org/vm/pharo/win/Pharo-VM-win-stable.zip Resolving files.pharo.org... 128.93.162.72 Connecting to files.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3324113 (3.2M) [application/zip] Saving to: âPharo-VM-win-stable.zipâ 0K .......... .......... .......... .......... .......... 1% 4.05M 1s 50K .......... .......... .......... .......... .......... 3% 8.18M 1s 100K .......... .......... .......... .......... .......... 4% 8.40M 0s 150K .......... .......... .......... .......... .......... 6% 8.17M 0s 200K .......... .......... .......... .......... .......... 7% 84.8M 0s 250K .......... .......... .......... .......... .......... 9% 8.85M 0s 300K .......... .......... .......... .......... .......... 10% 114M 0s 350K .......... .......... .......... .......... .......... 12% 8.78M 0s 400K .......... .......... .......... .......... .......... 13% 127M 0s 450K .......... .......... .......... .......... .......... 15% 8.58M 0s 500K .......... .......... .......... .......... .......... 16% 73.0M 0s 550K .......... .......... .......... .......... .......... 18% 119M 0s 600K .......... .......... .......... .......... .......... 20% 9.69M 0s 650K .......... .......... .......... .......... .......... 21% 55.9M 0s 700K .......... .......... .......... .......... .......... 23% 10.4M 0s 750K .......... .......... .......... .......... .......... 24% 120M 0s 800K .......... .......... .......... .......... .......... 26% 46.0M 0s 850K .......... .......... .......... .......... .......... 27% 10.4M 0s 900K .......... .......... .......... .......... .......... 29% 73.6M 0s 950K .......... .......... .......... .......... .......... 30% 10.0M 0s 1000K .......... .......... .......... .......... .......... 32% 103M 0s 1050K .......... .......... .......... .......... .......... 33% 63.2M 0s 1100K .......... .......... .......... .......... .......... 35% 10.2M 0s 1150K .......... .......... .......... .......... .......... 36% 47.0M 0s 1200K .......... .......... .......... .......... .......... 38% 10.6M 0s 1250K .......... .......... .......... .......... .......... 40% 103M 0s 1300K .......... .......... .......... .......... .......... 41% 93.0M 0s 1350K .......... .......... .......... .......... .......... 43% 9.44M 0s 1400K .......... .......... .......... .......... .......... 44% 120M 0s 1450K .......... .......... .......... .......... .......... 46% 109M 0s 1500K .......... .......... .......... .......... .......... 47% 74.5M 0s 1550K .......... .......... .......... .......... .......... 49% 11.8M 0s 1600K .......... .......... .......... .......... .......... 50% 53.3M 0s 1650K .......... .......... .......... .......... .......... 52% 80.0M 0s 1700K .......... .......... .......... .......... .......... 53% 48.3M 0s 1750K .......... .......... .......... .......... .......... 55% 12.7M 0s 1800K .......... .......... .......... .......... .......... 56% 83.6M 0s 1850K .......... .......... .......... .......... .......... 58% 78.6M 0s 1900K .......... .......... .......... .......... .......... 60% 12.5M 0s 1950K .......... .......... .......... .......... .......... 61% 66.0M 0s 2000K .......... .......... .......... .......... .......... 63% 85.4M 0s 2050K .......... .......... .......... .......... .......... 64% 93.2M 0s 2100K .......... .......... .......... .......... .......... 66% 11.2M 0s 2150K .......... .......... .......... .......... .......... 67% 137M 0s 2200K .......... .......... .......... .......... .......... 69% 55.3M 0s 2250K .......... .......... .......... .......... .......... 70% 98.0M 0s 2300K .......... .......... .......... .......... .......... 72% 11.2M 0s 2350K .......... .......... .......... .......... .......... 73% 111M 0s 2400K .......... .......... .......... .......... .......... 75% 76.4M 0s 2450K .......... .......... .......... .......... .......... 77% 92.3M 0s 2500K .......... .......... .......... .......... .......... 78% 93.9M 0s 2550K .......... .......... .......... .......... .......... 80% 10.2M 0s 2600K .......... .......... .......... .......... .......... 81% 79.3M 0s 2650K .......... .......... .......... .......... .......... 83% 131M 0s 2700K .......... .......... .......... .......... .......... 84% 122M 0s 2750K .......... .......... .......... .......... .......... 86% 95.9M 0s 2800K .......... .......... .......... .......... .......... 87% 11.8M 0s 2850K .......... .......... .......... .......... .......... 89% 116M 0s 2900K .......... .......... .......... .......... .......... 90% 102M 0s 2950K .......... .......... .......... .......... .......... 92% 92.0M 0s 3000K .......... .......... .......... .......... .......... 93% 87.8M 0s 3050K .......... .......... .......... .......... .......... 95% 12.8M 0s 3100K .......... .......... .......... .......... .......... 97% 109M 0s 3150K .......... .......... .......... .......... .......... 98% 71.0M 0s 3200K .......... .......... .......... .......... ...... 100% 119M=0.1s 2014-05-06 13:21:01 (22.8 MB/s) - âPharo-VM-win-stable.zipâ saved [3324113/3324113] + bash build-platform.sh -i One/Pharo -o Pharo2.0 -v 2.0 -t Pharo -p mac build-platform.sh: sources file not found (<https://ci.inria.fr/pharo/job/Pharo-2.0/ws/One/PharoV30.sources)> Build step 'Execute shell' marked build as failure Archiving artifacts Description set: SSH: Current build result is [FAILURE], not going to run.

May 6, 2014

Re: [Pharo-dev] [Vm-dev] bug on windows ioShowDisplay for bitdepth 16/8/4 (big endian)

by Nicolai Hess

2014-05-05 20:37 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Nicolai, > > > On Mon, May 5, 2014 at 12:06 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> 2014-04-03 17:51 GMT+02:00 karl ramberg <karlramberg(a)gmail.com>: >> >>> >>> I can confirm this bug on windows Cog. >>> >>> Cheers, >>> Karl >>> >>> >>> On Thu, Apr 3, 2014 at 10:11 AM, Nicolai Hess <nicolaihess(a)web.de>wrote: >>> >>>> >>>> There is still something wrong with byte/word swap in windows >>>> ioShowDisplay code >>>> attached are two screenshots >>>> squeak 4.5 image with cogvm from http://files.pharo.org/vm/cogmt/win/ >>>> pharo 30793 image with latest vm from >>>> http://files.pharo.org/vm/pharo/win/ >>>> showing this bug after setting the Display depth to 16 >>>> (Display newDepth:16) >>>> >>>> sqwin32window.c has three variants for doing the byte_swap/word_swap on >>>> bitdepths with big endian to convert to lsb >>>> >>>> This one is active and causes this error. >>>> # if __GNUC__ >= 3 >>>> # define BYTE_SWAP(w) __asm__("bswap %0" : "=r" (w) : "r" (w)) >>>> # define WORD_SWAP(w) __asm__("roll $16, %0" : "=r" (w) : "r" (w)) >>>> >>>> This one would work >>>> # else >>>> # define BYTE_SWAP(w) __asm__("bswap %%eax" : "=eax" (w) : "eax" (w)) >>>> # define WORD_SWAP(w) __asm__("roll $16, %%eax" : "=eax" (w) : "eax" >>>> (w)) >>>> >>>> This one, of course, works too >>>> # else >>>> # define BYTE_SWAP(w) w = (w << 24) | ((w & 0xFF00) << 8) | ((w >> 8) >>>> & 0xFF00) | (w >> 24) >>>> # define WORD_SWAP(w) w = (( (unsigned)(w) << 16) | ((unsigned) (w) >> >>>> 16)) >>>> >>>> This one is not there but would work (at least with gcc > 4.5 >>>> # define BYTE_SWAP_MY(w) __asm__("bswap %0" : "+r" (w)) >>>> # define WORD_SWAP_MY(w) __asm__("roll $16, %0" : "+r" (w)) >>>> >>>> But actually I don't know assembler and/or the gcc inline code syntax, >>>> so >>>> I don't know what is wrong with the first version :) >>>> >>>> Nicolai >>>> >>>> btw, you can not test this bug with the current squeak 4.5 all in on >>>> image, >>>> as it uses a rather old vm. >>>> >>>> Third screenshot: >>>> using the latest stable pharo-vm, it looks much more wrong, as there >>>> was another(?) bug that is fixed already(?) - i don't know :) >>>> >>>> >>>> >>>> >>> >>> >> >> >> Someone else can reproduce this? >> (eliot?, nicolas? ) >> It is easily fixable, I think. But I am not good at inline assembler. >> I'll open a mantis and fogbugz report. >> >> Yes, I can reproduce it. But I've not had time to check with a pre 3.x > and a post 3.x compiler to check what the right syntax is. I'm busy with > other stuff right now. Hopefully I'll get to this in a coupel of weeks. > Anyone else out there who can provide the right syntax for > > 2.95 > 3.4.x > 4.x > > I'd be very grateful and simply integrate the fix. > > -- > best, > Eliot > > Ok, thank you eliot. I think I know now way the first version does not work: __asm__("bswap %0" : "=r" (w) : "r" (w)) The compiler might generate code like this, just: bswap %ebx without initialisation of that register (although we declare "r"(w) as input). It behaves like that, because an output register is supposed to be overwritten :) and the bswap command only uses the %0 (the first register in the output : input register list). The proper way for defining an register as output-input (or read-write register) would be __asm__("bswap %0" : "+r" (w) ) Some asm-inline tutorials mention, this(the "+" constraint modifier) would not work on all compilers and prefer another older syntax: __asm__("bswap %0" : "=r" (w) : "0" (w)) (use the 0th output register for input too) But even the gcc2.95 doc ( http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_16.html#IDX955) lists "+" as allowed constraint modifier, so, I think it should work. I'll test this with different gcc versions and compare the compiler output (after I found out how to install multiple mingw versions :) ) nicolai

May 6, 2014

[ANN] ESUG 2014 registration is open

by Luc Fabresse

Hi all, We are happy to announce that the registration for the 2014 ESUG conference is now open. Pay attention that the early bird registration is until 16th of July. http://www.esug.org/wiki/pier/Conferences/2014/Conference-Registration In addition this year, there will be no warranty for social event or goody for people registrering on site. --- The ESUG board PS: please distribute widely and ensure it arrives in all mailing-lists

May 6, 2014

Re: [Pharo-dev] Skip startup actions

by Yuriy Tymchuk

Thank you! On 06 May 2014, at 11:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > ./pharo Pharo.image --no-default-preferences > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Skip-startup-actions-tp4757983p4758027.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 6, 2014

Re: [Pharo-dev] Skip startup actions

by Sean P. DeNigris

./pharo Pharo.image --no-default-preferences ----- Cheers, Sean -- View this message in context: http://forum.world.st/Skip-startup-actions-tp4757983p4758027.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 6, 2014

Re: [Pharo-dev] Usage of should: in tests

by Eliot Miranda

On Mon, May 5, 2014 at 1:40 PM, Carlo <snoobabk(a)gmail.com> wrote: > Hi > > Personally I think the main reason to use #should: is that debugging is > easier as you can more easily restart the block in Debugger and replay the > failing messages. i.e. think of the #should: as lazily running the code > whereas #assert: as being eager because it evaluates the argument > immediately. > Often Iâll use the #assert:equals: or #assert:description so that I can > more easily debug (by restarting the execution in the appropriate test > method). I have previously modified the #assert: method to be polymorphic > with a boolean or a block so I donât have to use #should: e.g. > > assert: aBoolean > aBoolean value ifFalse: > [self logFailure: 'Assertion failed'. > self defaultTestFailure signal: âAssertion failed']. > > Apart from this I agree with all the comments on the doubts of using > #should:. Converting #should: calls to #assert: calls is probably not worth > the effort unless the #assert: is made polymorphic against a boolean or a > block. > +1. But it's trivial to add value to assert: et al... > > Cheers > Carlo > > > On 01 May 2014, at 12:52 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi, > I see many usage of #should: in SciSmalltalk tests that could simply be > turned into #assert: or eventually #assert:equals: > Why wanting to use a block? > Other than #should:raise: and #shouldnt:raise:, I don't really see the > point of #should: alone anyway... > IMO should: should be deprecated, less is more. > I'm possibly the author of several of these #should: sends, so don't take > it personnally ;) > > P.S. or is it easier to restart the block in the Debugger? > I cross post to pharo-dev because it's a generic question, and there are a > few #should: sends in Pharo-3.0 too. > > > -- best, Eliot

May 5, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Yuriy Tymchuk

You are welcome and thanks for enthusiasm! On 05 May 2014, at 22:25, kilon alios <kilon.alios(a)gmail.com> wrote: > it worked like a charm , thank you very much Yuriy. Problem solved. Now I need to figure out how to use the system but thats for tomorrow. Will be back with any question I may have. > > > On Mon, May 5, 2014 at 10:38 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Please try to update to the latest version and execute scripts again (maybe even after deleting untracked files) > > Uko > > On 05 May 2014, at 21:35, kilon alios <kilon.alios(a)gmail.com> wrote: > >> thank you :) >> >> >> On Mon, May 5, 2014 at 9:52 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Ok, now Iâm looking into this >> >> On 05 May 2014, at 20:23, kilon alios <kilon.alios(a)gmail.com> wrote: >> >>> so anyone willing to help me ? I tried once today again I get the same error. >>> >>> Kilon-iMac:UpdatedPharoByExample kilon$ ./download.sh >>> >>> --2014-05-05 21:21:16-- https://ci.inria.fr/pharo-contribution/job/Pier3BookOnPharo20/lastSuccessfu… >>> >>> Resolving ci.inria.fr... 193.51.193.223 >>> >>> Connecting to ci.inria.fr|193.51.193.223|:443... connected. >>> >>> HTTP request sent, awaiting response... 404 Not Found >>> >>> 2014-05-05 21:21:17 ERROR 404: Not Found. >>> >>> >>> >>> >>> >>> >>> >>> On Sat, May 3, 2014 at 12:06 PM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> trying to get the file from my web browser gives me an error too so either the link is dead or servers are down, or something else ? at least looks like wget is working :) >>> >>> >>> On Sat, May 3, 2014 at 11:53 AM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> Ok Nicolas I followed its advice and it looks like you are correct.Wget get error on make but make install seemed to worked. >>> >>> But >>> >>> I am getting an error connecting to the servers is Inria servers down today ? >>> >>> this is the error >>> >>> kilon-imac:UpdatedPharoByExample kilon$ ./download.sh >>> >>> --2014-05-03 11:49:15-- https://ci.inria.fr/pharo-contribution/job/Pier3BookOnPharo20/lastSuccessfu… >>> >>> Resolving ci.inria.fr... 193.51.193.223 >>> >>> Connecting to ci.inria.fr|193.51.193.223|:443... connected. >>> >>> HTTP request sent, awaiting response... 404 Not Found >>> >>> 2014-05-03 11:49:16 ERROR 404: Not Found. >>> >>> >>> >>> Yuriy thanks for the advice I have command line tools because I am building Blender the 3d open source app on my iMac. I tried before installing wget with homebrew it failed too. >>> >>> >>> >>> On Fri, May 2, 2014 at 3:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> There is some black magic with wget. I think you have to install command line tools which get uninstalled on every update. Also if I remember correctly, Iâve installed it with home-brew. >>> >>> Uko >>> >>> On 02 May 2014, at 13:15, kilon alios <kilon.alios(a)gmail.com> wrote: >>> >>>> Thank you Yuriy >>>> >>>> I have tried to follow the installation instructions before on my iMAC but I was not successful installing wget. I tried building wget myself and it failed with errors, I tried using a binary of wget that I found online that failed too. >>>> >>>> But I will give it another try today when I get home where my macs are and share with you the exact errors I am experiencing. >>>> >>>> >>>> On Fri, May 2, 2014 at 1:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> Hi. >>>> >>>> Here is a repo for updated version of Pharo by example https://github.com/SquareBracketAssociates/UpdatedPharoByExample and it should be done in Pillar. >>>> >>>> Iâve added you to the team, so feel free to contribute. >>>> >>>> Uko >>>> >>>> >>>> On 02 May 2014, at 12:22, kilon alios <kilon.alios(a)gmail.com> wrote: >>>> >>>> > How I can help improve Pharo by Example , add chapters and update current ones for Pharo 3 ? >>>> > >>>> > What is the process ? >>>> >>>> >>>> >>> >>> >>> >>> >> >> > >

May 5, 2014

Re: [Pharo-dev] Usage of should: in tests

by Carlo

Hi Personally I think the main reason to use #should: is that debugging is easier as you can more easily restart the block in Debugger and replay the failing messages. i.e. think of the #should: as lazily running the code whereas #assert: as being eager because it evaluates the argument immediately. Often Iâll use the #assert:equals: or #assert:description so that I can more easily debug (by restarting the execution in the appropriate test method). I have previously modified the #assert: method to be polymorphic with a boolean or a block so I donât have to use #should: e.g. assert: aBoolean aBoolean value ifFalse: [self logFailure: 'Assertion failed'. self defaultTestFailure signal: âAssertion failed']. Apart from this I agree with all the comments on the doubts of using #should:. Converting #should: calls to #assert: calls is probably not worth the effort unless the #assert: is made polymorphic against a boolean or a block. Cheers Carlo On 01 May 2014, at 12:52 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: Hi, I see many usage of #should: in SciSmalltalk tests that could simply be turned into #assert: or eventually #assert:equals: Why wanting to use a block? Other than #should:raise: and #shouldnt:raise:, I don't really see the point of #should: alone anyway... IMO should: should be deprecated, less is more. I'm possibly the author of several of these #should: sends, so don't take it personnally ;) P.S. or is it easier to restart the block in the Debugger? I cross post to pharo-dev because it's a generic question, and there are a few #should: sends in Pharo-3.0 too.

May 5, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

it worked like a charm , thank you very much Yuriy. Problem solved. Now I need to figure out how to use the system but thats for tomorrow. Will be back with any question I may have. On Mon, May 5, 2014 at 10:38 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Please try to update to the latest version and execute scripts again > (maybe even after deleting untracked files) > > Uko > > On 05 May 2014, at 21:35, kilon alios <kilon.alios(a)gmail.com> wrote: > > thank you :) > > > On Mon, May 5, 2014 at 9:52 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: > >> Ok, now Iâm looking into this >> >> On 05 May 2014, at 20:23, kilon alios <kilon.alios(a)gmail.com> wrote: >> >> so anyone willing to help me ? I tried once today again I get the same >> error. >> >> Kilon-iMac:UpdatedPharoByExample kilon$ ./download.sh >> >> --2014-05-05 21:21:16-- >> https://ci.inria.fr/pharo-contribution/job/Pier3BookOnPharo20/lastSuccessfu… >> >> Resolving ci.inria.fr... 193.51.193.223 >> >> Connecting to ci.inria.fr|193.51.193.223|:443... connected. >> >> HTTP request sent, awaiting response... 404 Not Found >> >> 2014-05-05 21:21:17 ERROR 404: Not Found. >> >> >> >> >> >> On Sat, May 3, 2014 at 12:06 PM, kilon alios <kilon.alios(a)gmail.com>wrote: >> >>> trying to get the file from my web browser gives me an error too so >>> either the link is dead or servers are down, or something else ? at least >>> looks like wget is working :) >>> >>> >>> On Sat, May 3, 2014 at 11:53 AM, kilon alios <kilon.alios(a)gmail.com>wrote: >>> >>>> Ok Nicolas I followed its advice and it looks like you are correct.Wget >>>> get error on make but make install seemed to worked. >>>> >>>> But >>>> >>>> I am getting an error connecting to the servers is Inria servers down >>>> today ? >>>> >>>> this is the error >>>> >>>> kilon-imac:UpdatedPharoByExample kilon$ ./download.sh >>>> >>>> --2014-05-03 11:49:15-- >>>> https://ci.inria.fr/pharo-contribution/job/Pier3BookOnPharo20/lastSuccessfu… >>>> >>>> Resolving ci.inria.fr... 193.51.193.223 >>>> >>>> Connecting to ci.inria.fr|193.51.193.223|:443... connected. >>>> >>>> HTTP request sent, awaiting response... 404 Not Found >>>> >>>> 2014-05-03 11:49:16 ERROR 404: Not Found. >>>> >>>> >>>> Yuriy thanks for the advice I have command line tools because I am >>>> building Blender the 3d open source app on my iMac. I tried before >>>> installing wget with homebrew it failed too. >>>> >>>> >>>> On Fri, May 2, 2014 at 3:25 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: >>>> >>>>> There is some black magic with wget. I think you have to install >>>>> command line tools which get uninstalled on every update. Also if I >>>>> remember correctly, Iâve installed it with home-brew. >>>>> >>>>> Uko >>>>> >>>>> On 02 May 2014, at 13:15, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>> Thank you Yuriy >>>>> >>>>> I have tried to follow the installation instructions before on my iMAC >>>>> but I was not successful installing wget. I tried building wget myself and >>>>> it failed with errors, I tried using a binary of wget that I found online >>>>> that failed too. >>>>> >>>>> But I will give it another try today when I get home where my macs are >>>>> and share with you the exact errors I am experiencing. >>>>> >>>>> >>>>> On Fri, May 2, 2014 at 1:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: >>>>> >>>>>> Hi. >>>>>> >>>>>> Here is a repo for updated version of Pharo by example >>>>>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample and >>>>>> it should be done in Pillar. >>>>>> >>>>>> Iâve added you to the team, so feel free to contribute. >>>>>> >>>>>> Uko >>>>>> >>>>>> >>>>>> On 02 May 2014, at 12:22, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>>> >>>>>> > How I can help improve Pharo by Example , add chapters and update >>>>>> current ones for Pharo 3 ? >>>>>> > >>>>>> > What is the process ? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >> >> > >

May 5, 2014

Re: [Pharo-dev] IDE ideas: Theseus

by pharo4Stef＠free.fr

> I will have a look at what they are doingâ¦ > > Besides Opal, there is work being done (early stages, but now actively working on it) to add a Reflectivity-style > behavioral reflection to Pharo by default. I really want to see that :) > It will be interesting to see if this would be powerful enough for realising > IDE ideas like this. >

May 5, 2014