Re: Removing XFAILs from test suite summary

[Mike Miller]

On Wed, Apr 11, 2018 at 14:03:12 -0400, John W. Eaton wrote:
> On 04/11/2018 01:54 PM, Rik wrote:
> > My suggestion would be that we file a bug report for each remaining XFAIL
> > and then associate that bug report with the BIST tests.  This would at
> > least give us a place to track these things.  As it is, nobody ever really
> > reviews these.  At least with a bug report filed on Savannah there would be
> > a record of it.
> 
> Yes, I agree that all XFAILS should have bug report numbers associated with
> them.

Sounds good to me too.

However, there will always be one xtest without a bug number, because
the test function itself tests the xtest keyword.

> Is it possible that those five already have bug reports but the numbers were
> never recorded?  If not, then yes, we should create reports for them.

On my system,

  1 in gammainc.m
  1 in test.m
  1 in classdef.tst
  2 in jit.tst

There are no open bug reports about gammainc. I haven't looked into the
specifics of the classdef and jit test failures.

With grep, I also see several other %!xtests without bug numbers that
aren't failing on my system, but maybe fail on others, someone might
want to look into bug numbers for those as well.

-- 
mike

signature.asc
Description: PGP signature