Weird failure count if generic/210 fails without any output

[Qu Wenruo <wqu@suse.com>]

Hi,

Recently I'm hitting the following failure, the failure itself is a 
known one, but the point is there are two failures, but only reported one:

   Failures:  generic/747
   Failed 2 of 1091 tests

The missing one is generic/210, which fails like this:

   generic/210 1s ...  1s
          [failed, exit status 126]no qualified output

But it's not shown in the "Failures:" line.

Furthermore, I can no longer reproduce the failure on generic/210 just 
after checking out the latest patches-in-queue, and re-make.

This failure may be caused by my recent system update, which can lead to 
old binaries to fail to load due to changed .so libraries.

But this still makes me wonder, is there some error detection bug in the 
check script that can miss some test failures?

Thanks,
Qu