[Octave-bug-tracker] [bug #49138] FLTK found at configure but all fltk toolkit tests fail

[Mike Miller]

Follow-up Comment #8, bug #49138 (project octave):

Agree, we do need a way to differentiate between a test that is disabled
because we *know* it would fail (such as --without-foo-feature), and a test
that fails because of some run time condition that we may not have expected.

The latter are more similar to XFAILS, they are expected failures, but not
because of a bug, because of some external condition like not having a
display, or not having a home directory, or not having internet access.

We do want to see that the test failed, and why it failed, which is what is
shown now, but it would also be nice to be able to more easily see that they
are not failures due to a real problem in Octave or in some external library.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49138>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/