[Bioperl-l] Test errors on install (bioperl 1.6.0)

[Chris Fields]

Some of these failures appear to be coming from forked processes and  
appear sporadically, often if there is a network problem or server  
issue.  The giveaway is the odd # skipped/okay; you should also see  
something in the test harness summary at the end about 'error in TAP  
parsing' or similar.

We probably can fix that in the next point release to save and parse  
from a tempfile instead.

chris

On Jan 27, 2009, at 12:16 PM, Kevin Brown wrote:

> Installing on my system (CentOS 4.7) and spotted the following.
>
> t/RemoteDB/DB................................68/113
> #   Failed test at t/RemoteDB/DB.t line 226.
> #          got: '4'
> #     expected: '0'
>
> #   Failed test at t/RemoteDB/DB.t line 226.
> #          got: '4'
> #     expected: '0'
> t/RemoteDB/DB................................110/113
> #   Failed test at t/RemoteDB/DB.t line 226.
> #          got: '4'
> #     expected: '0'
> t/RemoteDB/DB................................ All 113 subtests passed
>        (less 748 skipped subtests: -635 okay)
>
> _______________________________________________
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-l