Re: [Valgrind-developers] Releasing 3.3.0

2008-02-11 Thread Bart Van Assche
On Feb 10, 2008 11:21 PM, Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > On Mon, 7 Jan 2008, Bart Van Assche wrote: > > >> After 3.3.0 is done we can merge make exp-regtest into standard make > >> regtest. > > > > Now that 3.3.0 has been released, can the aforementioned change please > > be imple

Re: [Valgrind-developers] Releasing 3.3.0

2008-02-10 Thread Nicholas Nethercote
On Mon, 7 Jan 2008, Bart Van Assche wrote: >> After 3.3.0 is done we can merge make exp-regtest into standard make >> regtest. > > Now that 3.3.0 has been released, can the aforementioned change please > be implemented ? I recommend to run the exp-drd regression tests only > on x86 and x86_64, an

Re: [Valgrind-developers] Releasing 3.3.0

2008-01-07 Thread Bart Van Assche
On Dec 3, 2007 1:35 PM, Julian Seward <[EMAIL PROTECTED]> wrote: > On Monday 03 December 2007 09:47, Tom Hughes wrote: > > In message <[EMAIL PROTECTED]> > > > > Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > > > I can either change the script to run 'make exp-regtest' -- which will > > >

Re: [Valgrind-developers] Releasing 3.3.0

2007-12-03 Thread Tom Hughes
In message <[EMAIL PROTECTED]> Julian Seward <[EMAIL PROTECTED]> wrote: >> My machines actually check the script out of the repository each >> night, so just updating the repository to run both would fix my >> machines. > > That's neat. So the top level cron command runs some other little

Re: [Valgrind-developers] Releasing 3.3.0

2007-12-03 Thread Julian Seward
On Monday 03 December 2007 09:47, Tom Hughes wrote: > In message <[EMAIL PROTECTED]> > > Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > > I can either change the script to run 'make exp-regtest' -- which will > > require Tom and Julian to update their copy of the script on those > > machi

Re: [Valgrind-developers] Releasing 3.3.0

2007-12-03 Thread Tom Hughes
In message <[EMAIL PROTECTED]> Nicholas Nethercote <[EMAIL PROTECTED]> wrote: > I can either change the script to run 'make exp-regtest' -- which will > require Tom and Julian to update their copy of the script on those machines > -- or we can change 'make regtest' run all of them. I'm

Re: [Valgrind-developers] Releasing 3.3.0

2007-12-03 Thread Nicholas Nethercote
On Fri, 30 Nov 2007, Bart Van Assche wrote: > Regarding the 3.3.0 release, a question about the nightly build: from > the nightly build output I can see that the exp-drd source code and > regression tests are compiled, but are the exp-drd regression tests > run during the nightly build ? I could n

Re: [Valgrind-developers] Releasing 3.3.0

2007-11-30 Thread Bart Van Assche
On Nov 22, 2007 7:53 PM, Julian Seward <[EMAIL PROTECTED]> wrote: > > Greetings all. > > I'm trying to wrap up the long overdue 3.3.0 release. Regarding the 3.3.0 release, a question about the nightly build: from the nightly build output I can see that the exp-drd source code and regression tests

Re: [Valgrind-developers] Releasing 3.3.0

2007-11-23 Thread Nicholas Nethercote
On Thu, 22 Nov 2007, Florian Krohm wrote: > Do you have plans to morph branches/ORIGIN_TRACKING into an > experimental tool? I read the pldi paper and understand it has > limitations but it could still make a quite a difference if a > bug is of the kind where it can track its origin. > I've checke

Re: [Valgrind-developers] Releasing 3.3.0

2007-11-22 Thread Florian Krohm
On Thursday 22 November 2007 1:53 pm, Julian Seward wrote: > Greetings all. > > I'm trying to wrap up the long overdue 3.3.0 release. It's been > nearly 18 months since 3.2.0 shipped. The 3.2.X line has done well, > but it's a bit old now. Plus we've accumulated a bunch of cool new > stuff to sh

[Valgrind-developers] Releasing 3.3.0

2007-11-22 Thread Julian Seward
Greetings all. I'm trying to wrap up the long overdue 3.3.0 release. It's been nearly 18 months since 3.2.0 shipped. The 3.2.X line has done well, but it's a bit old now. Plus we've accumulated a bunch of cool new stuff to ship over the past 18 months: * revised Massif (almost a complete rewr