Re: Jenkins set up for GNUstep...
Fred, I'm not certain how to compare it to Adam's old system since I wasn't intimately familiar with it. Jenkins is a continuous integration system. It checks out and builds the source periodically and reports any errors back to either the users who broke the build or to a given email address. I selected the gnustep-dev list because it seemed the most logical choice. I can change this so that it only sends it to me and a few others. Nevertheless I would like it to notify more than just me in case of a failure. It is, in fact, supposed to be a little annoying so that people are inspired to fix it when it breaks. ;) The way I have it configured right now is that it will ONLY notify the list if there is a failure; it should be silent otherwise. The website for Jenkins is here: http://jenkins-ci.org/ Jenkins is written in Java and can run on pretty much any platform we currently support. I noticed that you made all of the tests in gui as dashed hopes. That's fine.What I thought would be best, and I was going to check with you and Richard on this, is to add the tests for base first and then we could work on fleshing out the tests for gui a bit more and, when we're confident, we can add them to the jenkins build as well. I'm not sure how much good our testing framework does for us on GUI, though since, while it's easy to test Foundation/base with it, it's not very easy to test AppKit/gui. There's too much which depends on the eye and determining if it "looks" right in GUI. Later, GC On Wed, Mar 28, 2012 at 11:53 AM, Fred Kiefer wrote: > Could you please explain how this setup compares to the old nightly build > system that Adam used to provide? The benefit there was that it allowed > multiple machines to register as build hosts. Normally the build works fine > on the machine of the submitter, we need completely different setups to > detect the problems with submits. > It would be just great if there were an easy way to move over the old > distributed build farm to the new system. > > Running the tests on your machine is surely fine, but sending out mails on > failed tests may be a bit annoying. In gui we have a few tests that are > known failures. I am going to mark all of the as "dashed hopes" for now. The > problem here is that we want to encourage people to write more test code, if > a failed test ends up with a mail to everybody this may not send the right > message. > > Fred > > > On 28.03.2012 14:57, Gregory Casamento wrote: >> >> It shouldnt. It should be on a relatively high traffic list, since its >> important that the messages be recieved. >> >> No failed builds yet. ;). Im going to add the unit tests today. >> >> GC >> >> On Wednesday, March 28, 2012, Ivan Vučica wrote: >>> >>> Let's hope it doesn't end up spamming everyone tracking -dev ;) >>> >>> If it does, it may make sense to send those mails to a separate mailing >> >> list. >>> >>> On Wed, Mar 28, 2012 at 07:43, Gregory >>> Casamento >> >> wrote: Hey guys, I have set up a local Jenkins instance which builds GNUstep whenever there is a change. I have configured it to email the gnustep-dev@gnu.org list whenever the build is broken. Currently it is only configured to run the build itself, but I plan on adding the unit tests as well. This way we can see immediately when the build is broken or when one of the tests is broken. > > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: [Gnustep-cvs] r34822 - in /libs/base/trunk: ChangeLog Source/NSData.m
Hi, any other thoughts on this? I still think my proposed solution is the best
option: changing systemVersion to a fixed integer, and only incrementing it
when we make changes that break compatibility.
i.e. change NSCoder.m:
- (unsigned) systemVersion
{
return (((GNUSTEP_BASE_MAJOR_VERSION * 100)
+ GNUSTEP_BASE_MINOR_VERSION) * 100) + GNUSTEP_BASE_SUBMINOR_VERSION;
}
to:
- (unsigned) systemVersion
{
// Please increment when you make a change to the archive format
// that any older versions of the library won't be able to read, and
return 4;
}
We could also make a change in NSUnarchiver to check if the version of the
archive being read is greater than NSCoder's systemVersion, in which case we
won't be able to read the archive and can throw an exception (?).
-Eric
On 2012-03-07, at 4:00 PM, Eric Wasylishen wrote:
> Hm… to me it would make more sense if systemVersion was an arbitrary number
> that we increment only when we make a change to the archive format.
>
> If I understand it correctly, with the current scheme, an old version of
> gnustep-base can't tell if it is able to read an archive or not (it doesn't
> know that at 1.24.2 there was a change to the archive format). If we use
> arbitrary numbers, incremented when a format change is made, an old version
> of gnustep-base can tell for sure whether it can safely read an archive saved
> by a newer version of gnustep-base.
>
> Eric
>
> On 2012-03-07, at 1:16 AM, Richard Frith-Macdonald wrote:
>
>>
>> On 6 Mar 2012, at 09:32, Fred Kiefer wrote:
>>
There don't seem to be anyone using Gorm on OpenBSD from the packages.
I'd guess, otherwise, the problem would have shown up much earlier.
Therefore I'm not sure, whether there is a real need to fix that in
-base. But I definitely
should fix it in the Ports/Packages.
>>>
>>> I think you are wrong here. The mismatch of the archive numbers could not
>>> have caused any problem before the change to NSArchiver. This means, we
>>> don't know if any gorm files or other archives made on OpenBSD are
>>> affected. We have to plan for the worst and try to come up with a solution
>>> that allows for these archives to be read in correctly.
>>>
>>> I would like to propose an over cautious solution: We decouple the archiver
>>> systemVersion from the library version and make it bigger than any number
>>> already used on OpenBSD, lets say, library version + 4 (= 5.24.2). And make
>>> this the version that gets special treatment in NSArchiver, plus of course
>>> 1.24.2 (hopefully this specific number hasn't been used on OpenBSD), as we
>>> already have new archives produced with that number. And on OpenBSD, we
>>> need to guaranty that such mixing of version numbering never happens again.
>>> We also need to investigate the whole base code, whether there is another
>>> place where we might have such a mix.
>>
>> I've been thinking about this ... I really don't like the idea of separating
>> the value returned by -systemVersion from the version of the system ... it
>> just seems wrong.
>>
>> This is simply a bug in the OpenBSD package, nothing to do with GNUstep
>> directly ... but we ought to do a workaround.
>>
>> What I'd suggest is a temporary hack (meaning we should remove it in a few
>> years) to recognise version 4.0.0 as actually meaning 1.24.1 unless the
>> current system version is 4.0.0 or later, so that decoding old archives
>> works (though we should probably report the incident using NSLog()).
>>
>> Given that our version numbering increases really slowly, I wouldn't expect
>> us to actually get to version 4.0.0 for several years, by which time old
>> OpenBSD specific archives should not be an issue.
>> ___
>> Gnustep-dev mailing list
>> Gnustep-dev@gnu.org
>> https://lists.gnu.org/mailman/listinfo/gnustep-dev
>
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: gpbs and NSPasteboardCommunicationException
On 28.03.2012 16:22, Slex wrote: Il 28/03/2012 14:41, Riccardo Mottola ha scritto: Hi, which system are you on? Is it compiled cleanly? On a standard linux, NetBSD, FreeBSD and OpenBSD system, gpbs will be started automatically for you if it is not running. I suppose this is not working or it dies because of the error you get later on. Riccardo Slex wrote: Morning, finally i have updated my -make, -base, -gui, -back. After the last update for some reason gpbs is not auto-launched, so if i try to use some applications where i have to write, the window (textbox) is not update. Ok, no problem i done a script that launch at start of the session gpbs. The problem is that when i use some applications like editors or app that contains textboxes, now with gpbs started, i get lot of NSPasteboardCommunicationException. All works, but with that NSException: Error Occurred While Updating Menu Edit: NAME:NSPasteboardCommunicationException REASON:expected array count 18 and got 302141011 INFO:(null) This happens each time that i push a key button to write or i move around my desktop the app's window. Cheers, Slex For the moment i tried only on my linux (32bit) and it is standard. Effectively, before the new gnustep update/build, gpbs was started automatically and all did works fine; now i have to put it on .bashrc to be started, after the start it works, but with a lot of that output exception messages I will try soon on my FREEBSD-9 amd64. The error you are seeing comes from the array coding change Richard did a while ago. We all think that this is only possible when one of the involved applications (our test application or gpbs) is linked with an older version of GNUstep base. Could you please make sure that you remove all traces of old GNUstep installations from your machine. Next recompile all of GNUstep (make, base, gui, back, all used frameworks and your application) from scratch. If it still fails, try to find out which gpbs gets used. Either with "which gpbs" or if that fails by "find / -name gpbs". ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Jenkins set up for GNUstep...
Could you please explain how this setup compares to the old nightly build system that Adam used to provide? The benefit there was that it allowed multiple machines to register as build hosts. Normally the build works fine on the machine of the submitter, we need completely different setups to detect the problems with submits. It would be just great if there were an easy way to move over the old distributed build farm to the new system. Running the tests on your machine is surely fine, but sending out mails on failed tests may be a bit annoying. In gui we have a few tests that are known failures. I am going to mark all of the as "dashed hopes" for now. The problem here is that we want to encourage people to write more test code, if a failed test ends up with a mail to everybody this may not send the right message. Fred On 28.03.2012 14:57, Gregory Casamento wrote: It shouldnt. It should be on a relatively high traffic list, since its important that the messages be recieved. No failed builds yet. ;). Im going to add the unit tests today. GC On Wednesday, March 28, 2012, Ivan Vučica wrote: Let's hope it doesn't end up spamming everyone tracking -dev ;) If it does, it may make sense to send those mails to a separate mailing list. On Wed, Mar 28, 2012 at 07:43, Gregory Casamento wrote: Hey guys, I have set up a local Jenkins instance which builds GNUstep whenever there is a change. I have configured it to email the gnustep-dev@gnu.org list whenever the build is broken. Currently it is only configured to run the build itself, but I plan on adding the unit tests as well. This way we can see immediately when the build is broken or when one of the tests is broken. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: gpbs and NSPasteboardCommunicationException
Il 28/03/2012 14:41, Riccardo Mottola ha scritto: Hi, which system are you on? Is it compiled cleanly? On a standard linux, NetBSD, FreeBSD and OpenBSD system, gpbs will be started automatically for you if it is not running. I suppose this is not working or it dies because of the error you get later on. Riccardo Slex wrote: Morning, finally i have updated my -make, -base, -gui, -back. After the last update for some reason gpbs is not auto-launched, so if i try to use some applications where i have to write, the window (textbox) is not update. Ok, no problem i done a script that launch at start of the session gpbs. The problem is that when i use some applications like editors or app that contains textboxes, now with gpbs started, i get lot of NSPasteboardCommunicationException. All works, but with that NSException: Error Occurred While Updating Menu Edit: NAME:NSPasteboardCommunicationException REASON:expected array count 18 and got 302141011 INFO:(null) This happens each time that i push a key button to write or i move around my desktop the app's window. Cheers, Slex ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev For the moment i tried only on my linux (32bit) and it is standard. Effectively, before the new gnustep update/build, gpbs was started automatically and all did works fine; now i have to put it on .bashrc to be started, after the start it works, but with a lot of that output exception messages I will try soon on my FREEBSD-9 amd64. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Jenkins set up for GNUstep...
It shouldnt. It should be on a relatively high traffic list, since its important that the messages be recieved. No failed builds yet. ;). Im going to add the unit tests today. GC On Wednesday, March 28, 2012, Ivan Vučica wrote: > Let's hope it doesn't end up spamming everyone tracking -dev ;) > > If it does, it may make sense to send those mails to a separate mailing list. > On Wed, Mar 28, 2012 at 07:43, Gregory Casamento wrote: >> >> Hey guys, >> >> I have set up a local Jenkins instance which builds GNUstep whenever >> there is a change. >> >> I have configured it to email the gnustep-dev@gnu.org list whenever >> the build is broken. Currently it is only configured to run the build >> itself, but I plan on adding the unit tests as well. This way we can >> see immediately when the build is broken or when one of the tests is >> broken. >> >> Thanks, GC >> -- >> Gregory Casamento >> Open Logic Corporation, Principal Consultant >> yahoo/skype: greg_casamento, aol: gjcasa >> (240)274-9630 (Cell) >> http://www.gnustep.org >> http://heronsperch.blogspot.com >> >> ___ >> Gnustep-dev mailing list >> Gnustep-dev@gnu.org >> https://lists.gnu.org/mailman/listinfo/gnustep-dev > > > > -- > Ivan Vučica - i...@vucica.net > > -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: gpbs and NSPasteboardCommunicationException
Hi, which system are you on? Is it compiled cleanly? On a standard linux, NetBSD, FreeBSD and OpenBSD system, gpbs will be started automatically for you if it is not running. I suppose this is not working or it dies because of the error you get later on. Riccardo Slex wrote: Morning, finally i have updated my -make, -base, -gui, -back. After the last update for some reason gpbs is not auto-launched, so if i try to use some applications where i have to write, the window (textbox) is not update. Ok, no problem i done a script that launch at start of the session gpbs. The problem is that when i use some applications like editors or app that contains textboxes, now with gpbs started, i get lot of NSPasteboardCommunicationException. All works, but with that NSException: Error Occurred While Updating Menu Edit: NAME:NSPasteboardCommunicationException REASON:expected array count 18 and got 302141011 INFO:(null) This happens each time that i push a key button to write or i move around my desktop the app's window. Cheers, Slex ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
gpbs and NSPasteboardCommunicationException
Morning, finally i have updated my -make, -base, -gui, -back. After the last update for some reason gpbs is not auto-launched, so if i try to use some applications where i have to write, the window (textbox) is not update. Ok, no problem i done a script that launch at start of the session gpbs. The problem is that when i use some applications like editors or app that contains textboxes, now with gpbs started, i get lot of NSPasteboardCommunicationException. All works, but with that NSException: Error Occurred While Updating Menu Edit: NAME:NSPasteboardCommunicationException REASON:expected array count 18 and got 302141011 INFO:(null) This happens each time that i push a key button to write or i move around my desktop the app's window. Cheers, Slex ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Jenkins set up for GNUstep...
Let's hope it doesn't end up spamming everyone tracking -dev ;) If it does, it may make sense to send those mails to a separate mailing list. On Wed, Mar 28, 2012 at 07:43, Gregory Casamento wrote: > Hey guys, > > I have set up a local Jenkins instance which builds GNUstep whenever > there is a change. > > I have configured it to email the gnustep-dev@gnu.org list whenever > the build is broken. Currently it is only configured to run the build > itself, but I plan on adding the unit tests as well. This way we can > see immediately when the build is broken or when one of the tests is > broken. > > Thanks, GC > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell) > http://www.gnustep.org > http://heronsperch.blogspot.com > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev > -- Ivan Vučica - i...@vucica.net ___ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
