- Pharo-dev - lists.pharo.org

Fwd: [Pharo CI] Jenkins down 10/11 Feb

by Marcus Denker

This is todayâ¦ > > There will a big update of the Inria CI infrastructure. > > On 10 Feb the system will go offline 5PM Paris time, it will > be online the 12th hopefully latest. > > Why? For now the system just supports Win and Linux. > This update will add the base for MacOS vitual servers. > (If you wonder how it works now: we have a non-virtual > Mac in our office that runs all mac buildsâ¦) > > Marcus

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Pablo Herrero

Yeap, I evidently something got broken again recently I'll try to fix it ASAP.

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Pablo Herrero

2015-02-10 12:17 GMT-03:00 Nicolai Hess <nicolaihess(a)web.de>: > - But now, runing OC* tests half of them fail. > > - Executing OpalCompiler recompileAll throws some errors and > the images is really slow, constantly writing errors to the debugfile: > > [31mMessageNotUnderstood: RBArgumentNode>>start: > [0mRBArgumentNode(Object)>>doesNotUnderstand: #start: > RBArgumentNode(RBVariableNode)>>named:start: > RBArgumentNode class(RBVariableNode class)>>named:start: > RBArgumentNode class(RBVariableNode class)>>identifierNamed:at: > RBExplicitVariableParser>>parsePrimitiveIdentifier > RBExplicitVariableParser(RBParser)>>parseVariableNode > RBExplicitVariableParser(RBParser)>>parseKeywordPattern > RBExplicitVariableParser(RBParser)>>parseMessagePattern Ok, I'll take a look at that.

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Nicolai Hess

2015-02-10 15:27 GMT+01:00 Pablo Herrero <pablodherrero(a)gmail.com>: > I think I tried that before but it didn't work, maybe I did something > wrong then. > I changed the compiler to the old one. load your slice changed the compiler back to opal. - But now, runing OC* tests half of them fail. - Executing OpalCompiler recompileAll throws some errors and the images is really slow, constantly writing errors to the debugfile: [31mMessageNotUnderstood: RBArgumentNode>>start: [0mRBArgumentNode(Object)>>doesNotUnderstand: #start: RBArgumentNode(RBVariableNode)>>named:start: RBArgumentNode class(RBVariableNode class)>>named:start: RBArgumentNode class(RBVariableNode class)>>identifierNamed:at: RBExplicitVariableParser>>parsePrimitiveIdentifier RBExplicitVariableParser(RBParser)>>parseVariableNode RBExplicitVariableParser(RBParser)>>parseKeywordPattern RBExplicitVariableParser(RBParser)>>parseMessagePattern > > 2015-02-10 11:23 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > > Hi Pablo, > > > > I presume you have not noticed when you <Edit> the Fogbugz issue, there > are > > two header fields "Preload" & "Postload" , which may satisfy your need. > Add > > your code just like you would type it into a Workspace. > > > > cheers -ben > > > > On Tue, Feb 10, 2015 at 9:19 PM, Pablo Herrero <pablodherrero(a)gmail.com> > > wrote: > >> > >> Hello, > >> > >> I had this patch (for issue 11992) for a while now at the bug system. > >> The problem I'm having is that in order to to run the test suite > >> properly I need to run some code before merging the slice and then > >> just before running the test suite. And as a consequence, I'm not > >> notified whenever some other patch that gets integrated breaks my > >> code. > >> > >> I have read that you can use metacello to configure post and preLoad > >> hooks for a project. I'm not sure if this could work for the fogbugz > >> CI, also since you need to add a class in order to use metacello it > >> would probably get integrated into the image which is not what I > >> intend. > >> > >> Is there then some easy way so run some code before the CI merges the > >> patch and just before the test suite runs?. > >> > >> PS1: Sorry is the answer for this turns out being pretty obvious, I'm > >> not that familiar with metacello. > >> PS2: The issue haven't receive a lot of attention probably because > >> it's been at 'Work Needed' state since forever, maybe it would help if > >> the test suite passes. > >> PS3: Here's a link to the issue > >> > >> > https://pharo.fogbugz.com/f/cases/11992/Remove-tokens-from-the-AST-Core-Nod… > >> . > >> > >> Thanks, > >> Pablo > >> > > > >

Feb. 10, 2015

Spotter feature request - fully defined Class>>method lookup

by Ben Coman

When I am reading Fogbugz issues, often there are method references using the common convention "MCDefinitionIndex>>#add: for a fully defined reference. It would be nice to be able to copy/paste that fully defined reference into Spotter and get delivered straight to that method. You might still list other implementors of the method, but the fully defined reference would be at the top, or somehow highlighted. I might get around to trying to code this myself, but I mention it in case it catches the interest of Spotter core team. cheers -ben

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Ben Coman

I think for a while the monkey did not run them, but it was fixed. Have another ago :) On Tue, Feb 10, 2015 at 10:27 PM, Pablo Herrero <pablodherrero(a)gmail.com> wrote: > I think I tried that before but it didn't work, maybe I did something > wrong then. > > 2015-02-10 11:23 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > > Hi Pablo, > > > > I presume you have not noticed when you <Edit> the Fogbugz issue, there > are > > two header fields "Preload" & "Postload" , which may satisfy your need. > Add > > your code just like you would type it into a Workspace. > > > > cheers -ben > > > > On Tue, Feb 10, 2015 at 9:19 PM, Pablo Herrero <pablodherrero(a)gmail.com> > > wrote: > >> > >> Hello, > >> > >> I had this patch (for issue 11992) for a while now at the bug system. > >> The problem I'm having is that in order to to run the test suite > >> properly I need to run some code before merging the slice and then > >> just before running the test suite. And as a consequence, I'm not > >> notified whenever some other patch that gets integrated breaks my > >> code. > >> > >> I have read that you can use metacello to configure post and preLoad > >> hooks for a project. I'm not sure if this could work for the fogbugz > >> CI, also since you need to add a class in order to use metacello it > >> would probably get integrated into the image which is not what I > >> intend. > >> > >> Is there then some easy way so run some code before the CI merges the > >> patch and just before the test suite runs?. > >> > >> PS1: Sorry is the answer for this turns out being pretty obvious, I'm > >> not that familiar with metacello. > >> PS2: The issue haven't receive a lot of attention probably because > >> it's been at 'Work Needed' state since forever, maybe it would help if > >> the test suite passes. > >> PS3: Here's a link to the issue > >> > >> > https://pharo.fogbugz.com/f/cases/11992/Remove-tokens-from-the-AST-Core-Nod… > >> . > >> > >> Thanks, > >> Pablo > >> > > > >

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Pablo Herrero

I think I tried that before but it didn't work, maybe I did something wrong then. 2015-02-10 11:23 GMT-03:00 Ben Coman <btc(a)openinworld.com>: > Hi Pablo, > > I presume you have not noticed when you <Edit> the Fogbugz issue, there are > two header fields "Preload" & "Postload" , which may satisfy your need. Add > your code just like you would type it into a Workspace. > > cheers -ben > > On Tue, Feb 10, 2015 at 9:19 PM, Pablo Herrero <pablodherrero(a)gmail.com> > wrote: >> >> Hello, >> >> I had this patch (for issue 11992) for a while now at the bug system. >> The problem I'm having is that in order to to run the test suite >> properly I need to run some code before merging the slice and then >> just before running the test suite. And as a consequence, I'm not >> notified whenever some other patch that gets integrated breaks my >> code. >> >> I have read that you can use metacello to configure post and preLoad >> hooks for a project. I'm not sure if this could work for the fogbugz >> CI, also since you need to add a class in order to use metacello it >> would probably get integrated into the image which is not what I >> intend. >> >> Is there then some easy way so run some code before the CI merges the >> patch and just before the test suite runs?. >> >> PS1: Sorry is the answer for this turns out being pretty obvious, I'm >> not that familiar with metacello. >> PS2: The issue haven't receive a lot of attention probably because >> it's been at 'Work Needed' state since forever, maybe it would help if >> the test suite passes. >> PS3: Here's a link to the issue >> >> https://pharo.fogbugz.com/f/cases/11992/Remove-tokens-from-the-AST-Core-Nod… >> . >> >> Thanks, >> Pablo >> >

Feb. 10, 2015

Re: [Pharo-dev] Running some code at fogbugz CI

by Ben Coman

Hi Pablo, I presume you have not noticed when you <Edit> the Fogbugz issue, there are two header fields "Preload" & "Postload" , which may satisfy your need. Add your code just like you would type it into a Workspace. cheers -ben On Tue, Feb 10, 2015 at 9:19 PM, Pablo Herrero <pablodherrero(a)gmail.com> wrote: > Hello, > > I had this patch (for issue 11992) for a while now at the bug system. > The problem I'm having is that in order to to run the test suite > properly I need to run some code before merging the slice and then > just before running the test suite. And as a consequence, I'm not > notified whenever some other patch that gets integrated breaks my > code. > > I have read that you can use metacello to configure post and preLoad > hooks for a project. I'm not sure if this could work for the fogbugz > CI, also since you need to add a class in order to use metacello it > would probably get integrated into the image which is not what I > intend. > > Is there then some easy way so run some code before the CI merges the > patch and just before the test suite runs?. > > PS1: Sorry is the answer for this turns out being pretty obvious, I'm > not that familiar with metacello. > PS2: The issue haven't receive a lot of attention probably because > it's been at 'Work Needed' state since forever, maybe it would help if > the test suite passes. > PS3: Here's a link to the issue > > https://pharo.fogbugz.com/f/cases/11992/Remove-tokens-from-the-AST-Core-Nod… > . > > Thanks, > Pablo > >

Feb. 10, 2015

Re: [Pharo-dev] Your Glorp changes

by Sven Van Caekenberghe

Torsten, > On 10 Feb 2015, at 13:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Torsten, > > >> On 10 Feb 2015, at 13:18, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Hi Sven, >> >> there is a Glorp-SvenVanCaekenberghe.93 from 22 January 2015, 12:40:38.42634 pm >> which does not seem to be based on the latest version at that time >> (Glorp-TorstenBergmann.94, 16 January 2015) but is based on an older version >> Glorp-EstebanMaringolo.92. >> >> Will you reapply your changes or do a merge? >> >> You can use a clean Pharo 4.0 and load Glorp right from the config browser. >> >> Thx >> T. > > Haha, as you know, it is quite hard to manipulate the Glorp package, it is way too big (so it is a good idea that you try to do something about that). I tried several times with out of memory errors, then I reran the VM with higher memory settings, before committing my .93 version. > > I will try to do a merge later on. It went way easier than I remember, very weird. In any case, the merge is done: === Name: Glorp-SvenVanCaekenberghe.95 Author: SvenVanCaekenberghe Time: 10 February 2015, 3:08:09.493595 pm UUID: 03731890-b5f3-41e6-a1a8-89bff76b3796 Ancestors: Glorp-TorstenBergmann.94, Glorp-SvenVanCaekenberghe.93 Merging: TimeStamp is deprecated, use DataAndTime === Sven

Feb. 10, 2015

Re: [Pharo-dev] Create a user for jenkins

by Sebastian Tleye

Thanks Christophe! 2015-02-10 14:50 GMT+01:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > Hi Sebastian, > > Le 10 fÃ©vr. 2015 Ã 14:37, Sebastian Tleye a Ã©crit : > > > Hi All, > > > > I'd like to see some of the jenkins jobs of Pharo to have an idea how > they were created, I don't have a user in jenkins and when I want to see > the jobs as an anonymous user (read-only) jenkins throws an > java.lang.NullPointerException error. > > You don't need permissions to browse jobs but you need them if you want to > browse jobs configuration. > > > How can I create a user? I only need a user to see how the jobs were > created, I don't need to create or modify jobs. > > Create an account on https://ci.inria.fr and ask to join the project you > are interested in (pharo-contribution for example). > > Regards, > Christophe > > -- SebastiÃ¡n Tleye

Feb. 10, 2015