Re: [AMBER-Developers] Bugzilla?

From: Ben Roberts <>
Date: Mon, 12 Oct 2009 21:27:16 -0400

Hi Scott,

On Mon, 2009-10-12 at 19:24 -0400, Scott Brozell wrote:
> What link leads to bugzilla ? I didnt see it here:

See here:

Especially, look under the "Amber 11 test summaries" heading.

> Im not a fan of opening bugzilla up to the ignorant masses (users).
> > >
> > > 1. Are we actually using Bugzilla at present, and/or is there a
> > > consensus one way or the other about whether we should be doing so (the
> > > Wiki page notwithstanding)?
> >
> > Technically we are, although it is not being used as zealously as it should
> > be.
> Yes we are. But we are also still following the unwritten scientific
> programming approach of 'u found it, u fix.'
> So bugzilla is not a place where we track all of our mistakes for
> pedagogical/administrative/financial purposes.
> Of course there is a time limit; so if u found it and tried hard enough
> to fix it but couldnt then report it.

I understand, Scott. My particular difficulty is that I'm not well
versed in C programming (though I'm learning - slowly), and not terribly
familiar with the whole Amber code base yet. I can help to identify the
problem, and even run the code through a debugger to find out what
function is causing, for example, a segfault. But a problem that might
at the moment take me five days to fix could probably be fixed by
someone like you or Dave in half a day, if not indeed half an hour, and
with more confidence in the resulting code. I'm not trying to make extra
work for people; on the contrary, I'm trying to find the way I can best
help fix problems - that is, with the least amount of total effort. And
if I can't fix something myself, I would rather report it to someone who
can than sweep it under the carpet.

Some problems I probably can fix myself, even in C. But when I come
across things like 64-bit memory messes, you can perhaps see why I
wouldn't want to try my hand at fixing those myself just yet.

> Heres my blurb on bug reports:
> We gratefully accept detailed bug reports that contain short input
> files for reproducible bugs. In fact those are our favorite ones :)

I sent my original email with a view to the test suite in particular. In
general, I agree absolutely.


AMBER-Developers mailing list
Received on Mon Oct 12 2009 - 18:30:03 PDT
Custom Search