|
From: <dc...@us...> - 2005-11-14 20:48:42
|
I downloaded the valgrind source from the Source Repository on the valgrind web site. Can anyone tell me what I have? The heading above the svn command indicates that it is 3.0 development line. Is this a snapshot of the 3.1.0 development that may lag a couple of weeks behind? The bleeding edge of development? What exactly do I have here? How close is this to the 3.1.0 source that is scheduled for release at the end of November? I would like to do some testing of the 3.1.0 product on some of the IBM PowerPC machines to determine whether there are significant problems that don't show up on your PPC machines. I'd like to do the testing as early as possible (as well as after you make the official 3.1.0 release) so that hopefully any critical problems can be fixed in time to be pushed into the upcoming Linux distributions. I assume that the developers may have bug fixes that are in their own build areas but not necessarily in the Code Repository. How close would you expect the Code Repository valgrind be to the one that you are using to run nightly builds? What sort of variance with the nightly build test results would you expect me to see? |
|
From: Nicholas N. <nj...@cs...> - 2005-11-14 21:11:07
|
On Mon, 14 Nov 2005, dc...@us... wrote: > I downloaded the valgrind source from the Source Repository on the valgrind web > site. Can anyone tell me what I have? The heading above the svn command > indicates that it is 3.0 development line. Is this a snapshot of the 3.1.0 > development that may lag a couple of weeks behind? The bleeding edge of > development? Bleeding edge. I'll update the page to make it clearer. > What exactly do I have here? How close is this to the 3.1.0 source that is > scheduled for release at the end of November? Very close. More fixes will go in, but that's the code it will be based on. > I would like to do some testing of the 3.1.0 product on some of the IBM > PowerPC machines to determine whether there are significant problems that > don't show up on your PPC machines. I'd like to do the testing as early as > possible (as well as after you make the official 3.1.0 release) so that > hopefully any critical problems can be fixed in time to be pushed into > the upcoming Linux distributions. Great! > I assume that the developers may have bug fixes that are in their own build > areas but not necessarily in the Code Repository. Not many, if any. > How close would you expect the Code Repository valgrind be to the one > that you are using to run nightly builds? Exactly the same -- the nightly test scripts check the SVN code out. > What sort of variance with the nightly build test results would you > expect me to see? None, except for those caused by your machine being different. Hopefully they'll match well, but there's always a bit of variation. It'll be good to see your results. Nick |
|
From: Julian S. <js...@ac...> - 2005-11-15 01:13:39
|
> On Mon, 14 Nov 2005, dc...@us... wrote: > > I downloaded the valgrind source from the Source Repository on the > > valgrind web site. Can anyone tell me what I have? The heading above > > the svn command indicates that it is 3.0 development line. Is this a > > snapshot of the 3.1.0 development that may lag a couple of weeks behind? > > The bleeding edge of development? > > Bleeding edge. I'll update the page to make it clearer. Yes indeed -- literally up to the nanosecond. As you are subscribed to this list you will also get email notification of any further changes. > > What exactly do I have here? How close is this to the 3.1.0 source that > > is scheduled for release at the end of November? > > Very close. More fixes will go in, but that's the code it will be based > on. I hope that we will be at functionality freeze within the next 24 hours, then it's fixing and bug testing. > > I would like to do some testing of the 3.1.0 product on some of the IBM > > PowerPC machines to determine whether there are significant problems that > > don't show up on your PPC machines. I'd like to do the testing as early > > as possible (as well as after you make the official 3.1.0 release) Good. Start now. > > so > > that hopefully any critical problems can be fixed in time to be pushed > > into the upcoming Linux distributions. > > Great! Yup! > > I assume that the developers may have bug fixes that are in their own > > build areas but not necessarily in the Code Repository. > > Not many, if any. Bug fixes/functionality changes get flushed to the main repo very rapidly. To all intents and purposes, an svn checkout at any moment will give the the same as all the developers have. --- Make friends with the nightly build scripts, and get them going on your machines. Currently we're testing ppc32 on a 970 running YDL4, but we also use a Mac Mini running SuSE10 for development. Let us know how you get on. J |
|
From: Nicholas N. <nj...@cs...> - 2005-11-15 01:46:08
|
On Tue, 15 Nov 2005, Julian Seward wrote: > Make friends with the nightly build scripts, and get them going on your > machines. Currently we're testing ppc32 on a 970 running YDL4, but we > also use a Mac Mini running SuSE10 for development. Let us know how > you get on. See nightly/README.txt for some instructions on using the nightly scripts. Nick |