[tei-council] @min and @max

[Martin Holmes]

OK, so we would now expect this test to fail. How is that failure 
handled? I was under the impression that all tests expected to fail were 
in detest.xml, and the failure was handled by putting the expected error 
messages into expected-results/detest.log. But in the latest revision of 
that file shows no error regarding the @min and @max constraints here 
(which is as expected, because this test isn't in detest.xml).

Is this expected failure handled by editing the hudson-log-parse-rules 
such that the error message resulting from the failure is flagged as OK? 
If so, that means only someone with Jenkins powers can add such 
constraints to the system.

Cheers,
Martin

On 12-06-20 12:31 AM, Sebastian Rahtz wrote:
> the truth is that this is only part of the picture. the content model of<lg>  has also to be changed to ask
> for model.lLike_sequence in order for the @min and @max test to have an effect. If you look at the schema,
> it comes out with
>
> model.lLike = l | l | l? | l? | l? | l?
> model.lLike_alternation = l | l | l? | l? | l? | l?
> model.lLike_sequence = l, l, l?, l?, l?, l?
> model.lLike_sequenceOptional = (l, l, l?, l?, l?, l?)?
> model.lLike_sequenceOptionalRepeatable = (l, l, l?, l?, l?, l?)*
> model.lLike_sequenceRepeatable = (l, l, l?, l?, l?, l?)+
>
> where you can see why the standard model.lLike does not do the job.
>
> so now you should watch P5 build fail :-}
> --
> Sebastian Rahtz
> Head of Information and Support Group
> Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
>
>
>
>
>
> .
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)