You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has come up right before the 4.9.0 release, so I'm flagging it here rather than trying to fix it directly during the freeze:
Line 465 of extract-isosch.xsl issues a warning whenever a <sch:report> or <sch:assert> is a direct child of a <constraint> element. This warning is triggered by the following constraintSpec:
<constraintSpec ident="test_contextless_report" scheme="schematron" xml:lang="en">
<desc>This <gi>constraintSpec</gi> is invalid because it
has an <gi>sch:report</gi> that does not have a context
(i.e., does not have a <tag>sch:rule
context="…"</tag>.)</desc>
<constraint>
<sch:report test="false()">This rule never fires.</sch:report>
</constraint>
</constraintSpec>
This causes the warning to go into the build log and therefore the Jenkins build is tagged as unstable. Since this is a detest process, perhaps it's important that the warning message be triggered, but surely it should be captured in the detest.log and checked rather than output to the console. Not sure exactly what the solution should be here.
The text was updated successfully, but these errors were encountered:
This has come up right before the 4.9.0 release, so I'm flagging it here rather than trying to fix it directly during the freeze:
Line 465 of extract-isosch.xsl issues a warning whenever a
<sch:report>
or<sch:assert>
is a direct child of a<constraint>
element. This warning is triggered by the following constraintSpec:This causes the warning to go into the build log and therefore the Jenkins build is tagged as unstable. Since this is a detest process, perhaps it's important that the warning message be triggered, but surely it should be captured in the detest.log and checked rather than output to the console. Not sure exactly what the solution should be here.
The text was updated successfully, but these errors were encountered: