Re: [Tei-council] Jenkins builds failing and not failing

OK, I've set that value to 10000 explicitly in antbuilder.xml. That gets me past that error, and now I see the same errors as show up in Peter's log: BUILD: Check validity with nvdl, first examples with feasible validity, and then the valid ones ./run-onvdl p5.nvdl p5.xml Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Schema implementation error: This schema has abstract patterns, yet they are supposed to be preprocessed out already ./run-onvdl p5valid.nvdl v.xml Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Error: unrecognized element in ISO Schematron namespace: check spelling and capitalizationparam Schema implementation error: This schema has abstract patterns, yet they are supposed to be preprocessed out already Are these irrelevant distractions? They aren't suppressed in the tei-log-parse-rules file in the Jenkins repo. Cheers, Martin On 2021-02-01 10:12 a.m., Bauman, Syd wrote:

I very recently started having to increase the value of --maxdepth on my system when running that ant task. I think (but am not at all sure) it is because of my recent upgrade to a new OS, which involved a new version of libxslt and xsltproc, which maybe has a lower default value of maxdepth? Anyway, I set it to 10000 in one branch or PR somewhere, and that worked.

(The maxdepth is the number of recursive template call allowed before presumed infinite and thus failure. The Schematron skeleton XSLT stylesheet now used parses the values of XPaths a character at a time using a recursive template. They (the XPaths being parsed) can get very long, even moreso given that it does not perform whitespace normalization beforehand. I do not know what the default maxdepth used to be, but it is 3000 on my system now, and I tried 10000 and that worked.)

------------------------------------------------------------------------ *From:* Tei-council on behalf of Martin Holmes *Sent:* Monday, February 1, 2021 13:01 *To:* tei-council@lists.tei-c.org *Subject:* Re: [Tei-council] Jenkins builds failing and not failing I've figured out where mine is failing: it's on this bit of antbuilder.xml, which was recently changed by Syd and commented accordingly:

<!--           These next 2 are XSLT 1, which will not run in SaxonHE           9.8.0.5, which is what we are currently running. Thus I have           used `xsltproc` here. We could, alternatively, update to           SaxonHE 9.8.0.7 which hsa re-instated XSLT 1.0 compatability           mode. —Syd, 2020-11-28        -->        <exec executable="xsltproc" failonerror="true">         <arg line="--output p5odds.included.isosch"/>         <arg line="Utilities/iso_dsdl_include.xsl"/>         <arg line="p5odds.isosch"/>        </exec>

The failure looks like this:

xsltproc --output p5odds.included.isosch Utilities/iso_dsdl_include.xsl p5odds.isosch runtime error: file Utilities/iso_dsdl_include.xsl line 1433 element value-of xsltApplySequenceConstructor: A potential infinite template recursion was detected.

I think this was caused by Syd's commit in November, but I'm wondering if the fact that he didn't see the same error means that we have differing versions of xsltproc on our systems; my desktop and servers are running Ubuntu 20.04, and xsltproc --version gives me:

xsltproc --version

Using libxml 20910, libxslt 10134 and libexslt 820 xsltproc was compiled against libxml 20910, libxslt 10134 and libexslt 820 libxslt 10134 was compiled against libxml 20910 libexslt 820 was compiled against libxml 20910

Syd, what do you have? Peter, what's running on your server?

Cheers, Martin

On 2021-02-01 9:49 a.m., Martin Holmes wrote:

...

Hi all,

If you look at Peter's Jenkins, you'll see that the TEI-P5-Test-dev job appears to succeed (it's green). However, the console log for the latest build (653) shows 14 errors:

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.te...

On my Jenkins, the latest build (547) also fails, but differently:

https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins2.t...

I'm going to try to figure out why my build is failing, but I'm even more puzzled by the main Jenkins, which seems to be giving the impression that all is well. Peter, do you know what's happening here? NVDL errors seem to be ignored.

Cheers, Martin

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.lists...

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre