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

Calypso wishlist

by Stephane Ducasse

Hi denis - I would like to be able to define a method even in the class pane and that the system detects it automatically. - Then we are starting to reverse engineering the ecompletion system and I'm learning it. I would like to know if Calypso can communicate with ecompletion the fact that we are defining a method. Then I have to check how the system can know that we are typing method argument when defining the signature but I think that this is not related to calypso. Stef

Feb. 8, 2018

Iceberg experience report - synchronising README change made on github

by Ben Coman

Could the Iceberg gurus try and comment on the following workflow. Please familiarise with the first four commits here... https://github.com/Traadh/cloudflareun/network from these actions... "first commit" -- on github I created it as an unitialized repo to try to push a "new repo" to it per my other post, but when that failed from the command line I did `git init; git add README; git remote ...; git push ...`) "First Pharo code" -- cloned the repo with Iceberg, added a package, synchronised, added commit comment and clicked <Commit and push onto master> "Update class comment" -- edited the class comment, then from Iceberg synchronised, added commit comment and clicked <Commit and push onto master> "Updated README" -- on github, used the built-in editor to easily preview markdown. Clicked its <Commit directly to the master branch.> PROBLEM... Now I'm at a point having trouble synchronising Iceberg to pick up that last change. 1. Right-clicked on "cloudflareun" and chose "Synchronise repository..." 2. In [Update] tab, clicked <Fetch new versions> and listed under [commits to be imported] is "Updated README". Good. 3. Then clicked on <Pull> which I expected would load that commit into the Image, and a new commit "Merge with ref/remotes/origin/master" showed up in [commit to be imported] So now I'm lost. It seems the <Pull> only operates on the disk? But why does it create a merge commit? It should have fast-forwarded. Checking from the command line, only shows the first three commits are common with the github network graph. The fourth commit is the new merge commit. $ git log commit f49c64a7751f95712acc30dab692fc7e85e0c810 Merge: c818e9a 52ab6ac Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:55:34 2018 +0800 Merge with refs/remotes/origin/master commit c818e9adebeb6be001b202aa48da009be97920eb Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:42:57 2018 +0800 Update class comment. commit 6f2df89b219c56530412252ace96bc95eb78373a Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:37:01 2018 +0800 First Pharo code commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:31:28 2018 +0800 first commit Checking the remote... $ git log origin/master commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:31:28 2018 +0800 first commit Whoops... not what I expected but I don't think that affected anything now. Probably it was left over from early attempts to create a "new" "cloudflareun" repo. Try again... $ git remote --v origin git@github.com:Traadh/cloudflareun.git (fetch) origin git@github.com:Traadh/cloudflareun.git (push) traadh git@github.com:Traadh/cloudflareun.git (fetch) traadh git@github.com:Traadh/cloudflareun.git (push) $ git log traadh/master commit 587bed95c4b8fb3986c9962c9206405c81c99e3d Author: Ben Coman <github.com(a)ben.coman.com.au> Date: Thu Feb 8 11:54:20 2018 +0800 Updated README commit c818e9adebeb6be001b202aa48da009be97920eb Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:42:57 2018 +0800 Update class comment. commit 6f2df89b219c56530412252ace96bc95eb78373a Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:37:01 2018 +0800 First Pharo code commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:31:28 2018 +0800 first commit So there are the four commits matching github. So it seems that Iceberg's FETCH did the right thing updating the remote. But the disk working directory should have just fast-forwarded rather than merging. Now seeing both these commits... * Merge with ref/remotes/origin/master * Updated README in the one [New commits to be imported] seems to be mixing results from the working repo and the remote repo in a way that makes it hard to guess the consequence of any next action here. I do see a <Merge and load> option when I right-click on one of those commits. Perhaps the "load" means to load from the disk working directory into the Image(?) but its a bit hidden compared to the <Fetch> and <Pull> that are buttons. It seems dangerous to take that action right now, since I guess the Image would diverge from the disk working directory. FIXING... What I ended up doing was remove the "merge commit" from the disk working directory $ git reset --hard HEAD^ then opened a new Iceberg which for [Updates] only showed only the single commit "Updated README" fetched into the remote repo. Good. I right-clicked on that and did <Merge and load> which correctly fast-forwarded the disk working directory... $ git log commit 587bed95c4b8fb3986c9962c9206405c81c99e3d Author: Ben Coman <github.com(a)ben.coman.com.au> Date: Thu Feb 8 11:54:20 2018 +0800 Updated README commit c818e9adebeb6be001b202aa48da009be97920eb Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:42:57 2018 +0800 Update class comment. commit 6f2df89b219c56530412252ace96bc95eb78373a Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:37:01 2018 +0800 First Pharo code commit 52ab6ac696760a60fe56af57e45f2e2ceaaae35e Author: Ben Coman <btc(a)openInWorld.com> Date: Thu Feb 8 11:31:28 2018 +0800 first commit However the same "Updated README" commit still shows in [New commits to be imported] tab, but now its right-click menu item now shows only <Load> rather than <Merge and load>. So it seem to correctly identify the disk working directory is up to date but clicking on <Load> doesn't change anything. Perhaps because there is no Pharo code to load? Since only the README outside the "src" directory changed? Moving to the [Push] tab, this shows the four commits seen in the last `git log` This is confusing since I'd expect this to be empty since... $ git log > /tmp/x1 $ git log traadh/master > /tmp/x2 $ diff /tmp/x1 /tmp/x2 is empty Luckily clicking <Publish all> cleared out this list with no impact on github network graph https://github.com/Traadh/cloudflareun/network SUMMARY In the end I seem to got done what I needed. I'm enjoying Iceberg more and more as I rub off the rough edges my understanding it. Hopefully my report will help smooth things for others. My only remaining niggle is not being able to get rid of this "1 incoming", but maybe that will disappear when I've got a code update to upload. cheers -ben P.S. It might be if the Iceberg [Remotes] could have a "Log" menu item that worked like `git log`. P.P.S. I think more thought needs to be given to whether mixing updates from both the remote and disk working directory in the one pane is beneficial? As an alternative, perhaps some side-scrolling GTInspector-like panes Image <--> Working Directory <--> Remote <--> Server(github) would better represent the git model. Or maybe statically position those panes in one window with buttons on directed lines showing which way and how far a commit moves when that button is pushed.

Feb. 8, 2018

Iceberg - creating virgin repos

by Ben Coman

If in the System Browser I do <Add Package...> and work a bit on it, then later want to push it to a new github repo, what is the recommended procedure? As a rough guess I tried the "New repository" button, then added the package and a remote, but then trying to push gives me an error... LGit_GIT_EUNBORNBRANCH: Reference 'refs/heads/master' not found At the moment I've only had success first creating the repo on github, then cloning it - so I/m not sure how the "New repository" button is useful. cheers -ben

Feb. 8, 2018

[Pharo 7.0-dev] Build #509: 20254-Playground-should-ask-to-create-class-for-non-Existing-Globals

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

There is a new Pharo build available! The status of the build #509 was: SUCCESS. The Pull Request #806 was integrated: "20254-Playground-should-ask-to-create-class-for-non-Existing-Globals" Pull request url: https://github.com/pharo-project/pharo/pull/806 Issue Url: https://pharo.fogbugz.com/f/cases/20254 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 7, 2018

Re: [Pharo-dev] another file reference question

by Stephane Ducasse

Now what is the difference between / and resolve: because this is the only difference with my code. I used path because it was the only way I could make sense. I will update the documentation :( this will be my cross. On Wed, Feb 7, 2018 at 8:28 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx alistair > > Yes this is what I want. > I tried to copy (before your post and I do not recall that copy was > creating the intermediate folders). > > Stef > > > On Tue, Feb 6, 2018 at 1:14 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Stef, >> >> Assuming I understand what you're trying to do: >> >> This is broken out to hopefully make it clear what the steps are: >> >> | src srcPrefix dstPrefix dst | >> >> src := 'a/b/c/d.pi' asFileReference. >> srcPrefix := 'a' asFileReference. >> dstPrefix := 'result' asFileReference. >> dst := dstPrefix resolve: (src relativeTo: srcPrefix). >> dst >> >> >> At that point presumably you want: >> >> src copyTo: dst. >> >> >> Cheers, >> Alistair >> >> >> >> >> On 6 February 2018 at 21:50, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Thanks alistair >>> >>> What I want to know is a different of paths between two paths so that >>> after I can reproduce the structure under another folder. >>> Example >>> >>> a/b/c/d.pi >>> I should ''copy'' it into result folder and I should get >>> >>> result/b/c/d.pi >>> >>> now I compute the path >>> >>> What is the path of a/b/c/d.pi in a => b/c/d.pi and I should then >>> 'copy' to result/b/c/d.pi >>> >>> On Fri, Feb 2, 2018 at 11:26 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>>> Hi Stef, >>>> >>>> On 2 February 2018 at 20:58, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>> Then I do not get why / is expecting a string and cannot accept a path. >>>>> >>>>> Then I do not get why we have paths. >>>>> Stef >>>> >>>> Paths are intended to be internal, and not something you ever deal >>>> with directly. >>>> >>>> I'm not sure I understand what you want to do, but maybe try replacing >>>> #/ with #resolve:, e.g.: >>>> >>>> '/home' asFileReference resolve: 'user' asFileReference >>>> " File @ /home/user" >>>> >>>> >>>> or: >>>> >>>> '/home' asFileReference resolve: 'user' asFileReference path >>>> " File @ /home/user" >>>> >>>> >>>> Cheers, >>>> Alistair >>>> >>>> >>>>> On Fri, Feb 2, 2018 at 8:22 PM, Stephane Ducasse >>>>> <stepharo.self(a)gmail.com> wrote: >>>>>> HI >>>>>> >>>>>> I have the following scenario: >>>>>> >>>>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>>>>> asFileReference / >>>>>> 'book.pillar' >>>>>> >>>>>>>>> >>>>>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" >>>>>> >>>>>> ok it works. >>>>>> >>>>>> I want to update the contents of a target folder only if a file is >>>>>> missing or too old compared to a source. >>>>>> >>>>>> The idea is that I have a target folder and I need to know if a file >>>>>> located in the source tree should be copied under the target. >>>>>> So I compute the difference from the root of the source to the file >>>>>> and I want to apply this path to the target to check some file >>>>>> properties. >>>>>> >>>>>> now I do not understand how I can get the following working: >>>>>> >>>>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>>>>> asFileReference >>>>>> / >>>>>> >>>>>> ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' >>>>>> asFileReference path) >>>>>> relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo' >>>>>> asFileReference path) >>>>>> >>>>>> >>>>>> Stef >>>>> >>>> >>> >>

Feb. 7, 2018

Re: [Pharo-dev] another file reference question

by Stephane Ducasse

Tx alistair Yes this is what I want. I tried to copy (before your post and I do not recall that copy was creating the intermediate folders). Stef On Tue, Feb 6, 2018 at 1:14 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > > Assuming I understand what you're trying to do: > > This is broken out to hopefully make it clear what the steps are: > > | src srcPrefix dstPrefix dst | > > src := 'a/b/c/d.pi' asFileReference. > srcPrefix := 'a' asFileReference. > dstPrefix := 'result' asFileReference. > dst := dstPrefix resolve: (src relativeTo: srcPrefix). > dst > > > At that point presumably you want: > > src copyTo: dst. > > > Cheers, > Alistair > > > > > On 6 February 2018 at 21:50, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Thanks alistair >> >> What I want to know is a different of paths between two paths so that >> after I can reproduce the structure under another folder. >> Example >> >> a/b/c/d.pi >> I should ''copy'' it into result folder and I should get >> >> result/b/c/d.pi >> >> now I compute the path >> >> What is the path of a/b/c/d.pi in a => b/c/d.pi and I should then >> 'copy' to result/b/c/d.pi >> >> On Fri, Feb 2, 2018 at 11:26 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> Hi Stef, >>> >>> On 2 February 2018 at 20:58, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> Then I do not get why / is expecting a string and cannot accept a path. >>>> >>>> Then I do not get why we have paths. >>>> Stef >>> >>> Paths are intended to be internal, and not something you ever deal >>> with directly. >>> >>> I'm not sure I understand what you want to do, but maybe try replacing >>> #/ with #resolve:, e.g.: >>> >>> '/home' asFileReference resolve: 'user' asFileReference >>> " File @ /home/user" >>> >>> >>> or: >>> >>> '/home' asFileReference resolve: 'user' asFileReference path >>> " File @ /home/user" >>> >>> >>> Cheers, >>> Alistair >>> >>> >>>> On Fri, Feb 2, 2018 at 8:22 PM, Stephane Ducasse >>>> <stepharo.self(a)gmail.com> wrote: >>>>> HI >>>>> >>>>> I have the following scenario: >>>>> >>>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>>>> asFileReference / >>>>> 'book.pillar' >>>>> >>>>>>>> >>>>> "File @ /Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result/book.pillar" >>>>> >>>>> ok it works. >>>>> >>>>> I want to update the contents of a target folder only if a file is >>>>> missing or too old compared to a source. >>>>> >>>>> The idea is that I have a target folder and I need to know if a file >>>>> located in the source tree should be copied under the target. >>>>> So I compute the difference from the root of the source to the file >>>>> and I want to apply this path to the target to check some file >>>>> properties. >>>>> >>>>> now I do not understand how I can get the following working: >>>>> >>>>> '/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/_result' >>>>> asFileReference >>>>> / >>>>> >>>>> ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo/book.pillar' >>>>> asFileReference path) >>>>> relativeTo: ('/Users/ducasse/Workspace/FirstCircle/MyBooks/Bk-Writing/PharoBooks/Booklet-AMiniSchemeInPharo' >>>>> asFileReference path) >>>>> >>>>> >>>>> Stef >>>> >>> >> >

Feb. 7, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Stephane Ducasse

And please please please use BIG font is you want to show something. Stef On Wed, Feb 7, 2018 at 11:45 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > I made notes and will add a page with all the infos later today. (for > http://pharo.org/contribute ) > > Marcus > > > On 5 Feb 2018, at 16:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Ah, Esteban's PR review tool is exactly what I was looking for. It works ! > > Still, please, please (Pavel) write down somewhere what you just explained > to me, else it will eventually be lost. > > Docs needed > > (1) contribute to Pharo (we have that) > (2) keep in sync once you have done (1) (we have that, but not about image > side) > (3) review pull requests of others (new, this email to start) > > Anyway, thanks for the answers. > > On 5 Feb 2018, at 15:10, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > 2018-02-05 13:54 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > With pull requests, it is relatively easy to see what changed in GitHub. > > Eg. Marcus' latest fix: > > https://github.com/pharo-project/pharo/pull/797 > > shows 6 files/classes changed, reasonably readable diff. > > How does one review such a PR in an image, to test it out ? > > > The easiest way is to download an image bootstrapped from that PR. > Next to the commits you have a validation status (red cross here), > click on it, go to "Artifacts" and then download the image > (bootstrap-cache/Pharo7.0-32bit-6ccdd62.zip) > > Esteban did a Pull request review tool: > > - register your local Pharo repository copy to Iceberg > - in the "Remotes" open context menu on the pharo-project remote (not > origin, which is probably our fork) > - GitHub - Review pull requests... > - open context menu on an issue and select "Review pull request..." > - select the newest commit and check changes > - to test it locally, do "Merge into image", answer "Yes" > > Has someone written a guide on how to do this best/most-easily ? > > > No idea, but Esteban presented that several times on ESUG and other places. > > How is/can this be related to contributing ? > > > If you want to use the PR review tool, you should have own fork and > local repository - the same for contributing > > If you then want to propose a modification fo the PR, you already have > a branch from the PR merging. > - do your change and synchronize the repository so your branch will be > present on your fork. > - then go to "Remotes" tab, open context menu on "MarcusDenker" remote > (it will be created during merging of the PR into your image) and then > do pull request. > - in Head select your fork and your issue branch name > - in Base select Marcus/Denker/pharo and the issue branch name > - click on Create Pull request > > It will create a PR on the repository that Marcus has. Like > https://github.com/MarcusDenker/pharo/pull/1 > When he will merge it, his PR to on Pharo repository will be updated > automatically. > > Cheers, > -- Pavel > > > Sven > > > >

Feb. 7, 2018

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

by Stephane Ducasse

Thanks for pushing this. I plan to work on migrating the seaside book to pillar when I'm done with the moose book and the magritte booklet. Stef On Wed, Feb 7, 2018 at 1:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems. > > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load. > > Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ? > > This is _really_ important to make progress, IMHO. > > I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine. > > Sven > >> On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> OK, Max, thanks for the reply. >> >> I will ask on the Pharo ML as well. >> >> I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. >> >>> On 6 Nov 2017, at 09:40, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Hi Sven, >>> >>> We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend. >>> >>> How urgent is the situation for you? >>> >>> Cheers, >>> Max >>> >>> >>> On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: >>> >>>> Hi, >>>> >>>> I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: >>>> >>>> project: 'Bootstrap' with: [ >>>> spec >>>> className: 'ConfigurationOfBootstrap'; >>>> repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; >>>> versionString: #stable ] >>>> >>>> I also tried the following: >>>> >>>> Metacello new >>>> baseline:'Seaside3'; >>>> repository: 'github://SeasideSt/Seaside:master/repository'; >>>> load. >>>> >>>> What is the right/recommended way to do it ? >>>> >>>> Thx, >>>> >>>> Sven >>>> >>>> _______________________________________________ >>>> seaside-dev mailing list >>>> seaside-dev(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >>> _______________________________________________ >>> seaside-dev mailing list >>> seaside-dev(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> > >

Feb. 7, 2018

Re: [Pharo-dev] VMs build process restored

by Stephane Ducasse

Yes thank you both! Stef On Tue, Feb 6, 2018 at 6:52 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Thank you very much Esteban, Thanks Fabio. > > On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> (it was broken since december) >> >> Which means latest vm versions are latest builds from OSVM: >> >> 64bit >> >> â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip >> â¢ >> http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip >> 32bit >> >> â¢ >> http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip >> >> Hints >> >> â¢ MacOS VMs now are signed! This should fix a lot of problems we >> had before. >> â¢ Please take note that win64 build lacks all library >> dependencies, and many things will not work (working on that). >> Thanks to Fabio to help me put all the pieces together. >> >> >> cheers, >> Esteban > > > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Feb. 7, 2018

[Pharo 7.0-dev] Build #508: 21248-Add-possibility-to-skip-some-tests-on-CI

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

There is a new Pharo build available! The status of the build #508 was: SUCCESS. The Pull Request #808 was integrated: "21248-Add-possibility-to-skip-some-tests-on-CI" Pull request url: https://github.com/pharo-project/pharo/pull/808 Issue Url: https://pharo.fogbugz.com/f/cases/21248 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 7, 2018