[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] new release and SuSE Linux

From: Tim Daly
Subject: Re: [Axiom-developer] new release and SuSE Linux
Date: Thu, 17 Jun 2010 04:08:05 -0400
User-agent: Thunderbird (Windows/20090302)

Great. The testing feedback is always welcome.

I'm bogged down right now working through another
CATS integration test suite. Lots of interesting
things are turning up.

I spend a week every 2 months looking at build issues
and general "product cleanup" just before each release.
The next scheduled release is July, likely July 23 if
history is any guide. Hopefully SUSE11.1 will be out
by then. I'll also take a deeper look at the build farm
idea you mentioned.


Martin Baker wrote:

OK, looks like you have things well in hand and you are obviously very busy with all this so it probably best if I don't take up any more of your time now.

Just for the record this is the issue that I was seeing (in the unlikely event that your tests could have missed it).

When I first started using Axiom last year with the May 2009 release and openSUSE 11.1 and I was getting:

System error:
Unknown bfd format

whenever draw was called or when I tried to compile an SPAD file.

However since then there have been lots of new versions of Axiom and a new version of openSUSE and I must admit I have lost track of which combinations that I have tried and if I added:
ulimit -v unlimited
to the startup script.

So when you release the new software I will try it and let you know if there is still an issue (openSUSE 11.3 is coming soon so I will try on that).


Martin Baker

On Wednesday 16 Jun 2010 20:08:42 Tim Daly wrote:
I looked at the build farm wiki but it is confusing.
I don't have the "skills and knowledge" to do this either :-)

I'll look into this server farm. At the moment I have a local
machine that does a SUSE build. What is the problem you are
seeing that needs to be solved?

I used to build Axiom on an HP server farm but that died.
I used to build Axiom on a slashdot server farm but that died.
Eventually I gave up and created my own server farm.
Currently I have 9 machines in my home office.
I need some other machines but cost is an issue (who said free
software is free? :-) )

Camm Maquire is currently updating the Debian version of
Axiom to a recent release. He is also working to fix the
issues with Mac OS X so stay tuned.

I tried to create a "cloud server farm". At the May release
I built a cloud machine on Amazon's cloud and successfully
compiled Axiom there. However this was only for one system.
I ran out of time to really study the problem. I would like to
have a large set of cloud machines set up and ready to go at
release time since it takes a few days to do a release, mostly
in doing hand-build/hand-checking of binaries.

Axiom is in "continuous build" locally. Every update of Axiom's
silver version is built and tested before the sources are pushed to
the silver hosts, currently about 3-4 times a day. The limiting
factor is the number of stupid mistakes I make which, fortunately,
rarely get passed the local build server checks.

Silver sources live on:

Axiom Gold version is at github. Gold is updated every 2 months.


Martin Baker wrote:

Would it be possible to check the planned new release under SuSE Linux
(because on  SuSE the virtual memory limit is set low by default).

All that is necessary to check the problem is to run something that uses
a bit of memory like draw and also to try to compile something from the
command line. That is )co somefile.

and if required put:

ulimit -v unlimited

in the startup script. Or at lest put a warning about this on the release

Even better would be to put into the SuSE build service like OpenAxiom
have done.  As you can see here:

this automatically generates rpms not only for SuSE but also for Fedora,
Mandriva, etc.

Unfortunately I don't have any skills or knowledge in doing this
otherwise I would offer to help.

Martin Baker

Axiom-developer mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]