This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ACATS tests that fail valgrind check



On Jan 12, 2005, at 05:53, Duncan Sands wrote:


I plan to enter all these reports into bugzilla, then start analysing them to
see which ones are bogus (it is good to have bogus reports and a note saying
they are bogus in bugzilla, since it will save time if someone else sees the
same valgrind failures).

It doesn't make sense to open reports for every test that valgrind flags.
For example, all the tasking tests most likely run into the same valgrind
manipulation. Please don't open tons of reports for this, it only causes
much extra work in maintaining the bug database.


Maybe it makes more sense to open one bug for all valgrind failures
and then open separate reports for each category of bug that you find to
be valid in at least some case, listing all tests affected by the bug.

Thanks,
  Geert


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]