Re: gputils QA

View: New views
2 Messages — Rating Filter:   Alert me  

Re: gputils QA

by David Barnett-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri, Mar 13, 2009 at 4:38 PM, Peter Keller <psilord@...> wrote:

> Out of curiosity, how do you build and test this software? Do you have
> nightly
> regression tests and on how many architectures? Or is it more sporadic,
> like a few people get together and pound on it a bit just before a release?

It's all much less formal than that. The long and short of it is that the
developers run the tests on every new commit, and then we assume it's good
until we hear otherwise =). We have a fair number of people running the
latest SVN version at any given time, and I believe we have a good number of
platforms represented, so anyone who finds a problem in SVN reports it in
our bug tracker and downgrades to an earlier version until we fix it (or
sometimes fixes it themselves). Then we just try to fix any critical bugs
before making a release. If a major bug does get into a release, then again
people can downgrade or use an SVN version. It sounds pretty helter-skelter,
but it's worked well for us.

David

Re: gputils QA

by Peter Keller :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri, Mar 13, 2009 at 07:35:19PM -0400, David Barnett wrote:
> It sounds pretty helter-skelter, but it's worked well for us.

Well, given that this command with the latest valgrind on the latest
trunk sources

valgrind --trace-children=yes --leak-check=full sh -x ./test all > & test.log

produced *no* memory errors in any of the tools except for some memory leaks,
which aren't that important in transient processes, I'd say the QA system you
have works exceedingly well. :)

-pete

---------------------------------------------------------------------
To unsubscribe, e-mail: gnupic-unsubscribe@...
For additional commands, e-mail: gnupic-help@...