<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello,<br>
<br>
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.<br>
This is currently the case for instance for<br>
<br>
test_run graphics datatipSetDisplay<br>
test_run graphics bug_10298<br>
test_run cacsd bug_13359<br>
test_run cacsd bug_15827<br>
<br>
that all are broken by the <a
href="http://bugzilla.scilab.org/show_bug.cgi?id=15790">bug
15790</a>.<br>
</p>
<p>Currently, we tend to reopen these tests with the "<-- NOT
FIXED -->" tag. <br>
But this processing is not really fair. It is rather puzzling.<br>
<br>
As a general policy, i am not in favour of multiplying the number
of available tags.<br>
However, what about creating a new one to point this situation?<br>
It could be<br>
<tt> // <-- BROKEN --> by 15790</tt><tt><br>
</tt>Such a test would be skipped, and in the test_run report,
"skipped: broken by 15790" would be displayed.<br>
<br>
What do you think about this proposal?<br>
<br>
Regards<br>
Samuel<br>
<br>
</p>
</body>
</html>