[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Test suite regressions vs expected failures
From: |
Mike Miller |
Subject: |
Test suite regressions vs expected failures |
Date: |
Wed, 16 Aug 2017 17:45:03 -0700 |
User-agent: |
NeoMutt/20170609 (1.8.3) |
Rik,
You may have missed the discussion about a month ago [1], but there are
four tests that you added to the test script "for.tst" that are failing
with the new "regression" status. You added these tests as part of the
fix for bug #50893 [2].
I'm not completely sure what the intent was, were these tests supposed
to pass as part of the bug fix? Or was your intent to add them as xtests
that fail because of behavior we are intentionally not following (a test
of a "won't fix" feature)?
In [1] we didn't really come to any conclusions about whether we want to
add tests for things that are "won't fix", or whether to mark them
somehow so they aren't flagged as regressions. But that's how they look
for now.
[1]: https://lists.gnu.org/archive/html/octave-maintainers/2017-07/msg00040.html
[2]: https://savannah.gnu.org/bugs/?50893
--
mike
signature.asc
Description: PGP signature
- Test suite regressions vs expected failures,
Mike Miller <=