Hello,
I am wondering about the processing of any unitary or non-regression
test that fails not because the bug that it tests is back, but because
another external bug breaks the code of the test.
This is currently the case for instance for
test_run graphics datatipSetDisplay
test_run graphics bug_10298
test_run cacsd bug_13359
test_run cacsd bug_15827
that all are broken by the bug 15790
<http://bugzilla.scilab.org/show_bug.cgi?id=15790>.
Currently, we tend to reopen these tests with the "<-- NOT FIXED -->" tag.
But this processing is not really fair. It is rather puzzling.
As a general policy, i am not in favour of multiplying the number of
available tags.
However, what about creating a new one to point this situation?
It could be
// <-- BROKEN --> by 15790
Such a test would be skipped, and in the test_run report, "skipped:
broken by 15790" would be displayed.
What do you think about this proposal?
Regards
Samuel
_______________________________________________
dev mailing list
dev@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/dev
