This is the mail archive of the mailing list for the GDB 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: c++/544: gdb.c++/annota2.exp: annotate-quit test sometimes fails

I ran annota2.exp 10 times with my usual testbed for a total of 380 test
runs.  annotate-quit had 380 PASSes and 0 non-PASSes.  This is for gdb
HEAD date '2003-02-06 19:11:07 UTC'.

The last report had gdb HEAD date '2003-02-05 07:30:23 UTC' and it had
5 PASS, 33 KFAIL for this test.  This has been typical for years.

(By the way, those dates are exact arguments to "cvs -D '...' checkout".
I used to do "cvs checkout" and record the date in an XML file.
Now I look at my clock (which is NTP sync'ed), subtract a couple
of minutes, and do "cvs -D '...'" on that date.  So the date should
be exactly reproducible for stuff like "cvs diff -D ... -D ...".
Thanks to Andrew C for that tip).

I diff'ed 2003-02-05 07:30:23 UTC and 2003-02-06 19:11:07 UTC.  The only
patch of interest is the big Ingham/Seitz/Zannoni/Cagney interpreter
change.  Fred Fish checked in a precedence fix to infttrace.c but the
only effect of that fix is to change some gdb debugging messages.

The cool part is that we will leave all the code in gdb.c++/annota2.exp
exactly the same, so that we will get KFAIL's again if the bug comes
back, and the KFAIL's will point to the PR, and the PR has this thread
in the audit trail.  We can edit the comments in annota2.exp to reflect
our new knowledge.

I would like to put the PR into 'feedback' state for 30 days, and then
close it.

Michael C

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