MySQL Bugs: #32674: Pushbuild test failure xref does not report all failures

Bug #32674	Pushbuild test failure xref does not report all failures
Submitted:	23 Nov 2007 17:48	Modified:	10 Dec 2008 14:02
Reporter:	Ingo Strüwing	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tools: Pushbuild	Severity:	S2 (Serious)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	pb1

Description:
"Pushbuild test failure xref" does not report all failures.

The reports often end in September or October. However sometimes recent failures show up.

Example: Enter 'rpl_row_sp002_innodb' (without the quotes) in the "Test name:" field, have '50' in "Max. number of rows:" and all other entries blank.

You will find "2007-09-12 15:10:27" as the latest failure for this test case. But there is definitely a failure of 2007-11-22: https://intranet.mysql.com/secure/pushbuild/getlog.pl?dir=mysql-6.0-engines&entry=istruewi...
(This is one day ago. I let the system some time...)

Counter-example: 'grant_cache' reports a failure of 2007-11-21 20:41:54, which looks reasonable.

How to repeat:
See the example in the bug description.

This is likely because xref is too picky with test names. Note that you must include both the suite and the combination under which the test was run in the search. In this case, it would be one of:

 rpl.rpl_row_sp002_innodb 'stmt'
 rpl.rpl_row_sp002_innodb 'mixed'
 rpl.rpl_row_sp002_innodb 'row'
 rpl.rpl_row_sp002_innodb

Still, this is of course very irritating and since there is no documentation for xref, it likely causes many test failures to go unnoticed.

Pushbuild2's xref does not require this workaround anymore.