[postgis-devel] Travis eating Doc errors?

[Martin Davis]

And rightly so...  I will add make check to my personal doc workflow.


On Tue, Mar 12, 2019 at 2:40 PM Paul Ramsey <pramsey at cleverelephant.ca>
wrote:

> Aha! Line 1031! What was I thinking…? :)
> P
>
> On Mar 12, 2019, at 2:36 PM, Darafei Komяpa Praliaskouski <me at komzpa.net>
> wrote:
>
> Here it is, just a bit earlier due to parallel build:
> https://travis-ci.org/postgis/postgis/jobs/505434125#L1031
>
> On Wed, Mar 13, 2019 at 12:28 AM Paul Ramsey <pramsey at cleverelephant.ca>
> wrote:
>
>> Martin just made a doc PR with a small docbook error and got this very
>> unhelpful failure in CI
>>
>> https://travis-ci.org/postgis/postgis/jobs/505434125
>>
>> Contrariwise, if I actually run ‘make check’ myself in ./doc I get the
>> actually useful feedback:
>>
>> Sparrow:~/Code/postgis-git/doc pramsey(dr-jts-doc-improve-ref)$ make check
>> /usr/bin/xmllint --loaddtd --xinclude --valid postgis-out.xml > /dev/null
>> reference_transaction.xml:15: element abstract: validity error : Element
>> abstract content does not follow the DTD, expecting (title? , (formalpara |
>> para | simpara)+), got (para note )
>>     </abstract>
>>                ^
>> make: *** [check] Error 4
>>
>> Any travis experts know why our setup is swallowing the error from make
>> check in ./doc?
>>
>> P
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
>
> --
> Darafei Praliaskouski
> Support me: http://patreon.com/komzpa
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20190312/351acebd/attachment-0001.html>