Project

General

Profile

Bug #2744

osmo-gsm-manuals master branch build is broken with "parser error : ATTLIST: no name for Attribute"

Added by neels 7 months ago. Updated 5 months ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
12/13/2017
Due date:
% Done:

0%

Estimated time:
Spec Reference:

Description

The current osmo-gsm-manuals master build is broken with the following error.
I cannot reproduce the error on my debian testing system, where the OsmoBSC manual builds fine.

+ xsltproc -o generated/combined.xml --stringparam with /home/osmocom-build/jenkins/workspace/osmo-gsm-manuals/OsmoBSC/vty/libbsc_vty_additions.xml /home/osmocom-build/jenkins/workspace/osmo-gsm-manuals/libosmocore/doc/vty/merge_doc.xsl generated/combine_src.xml
+ '[' -n '' ']'
xsltproc ../vty_reference.xsl generated/combined.xml \
    > generated/docbook_vty.xml
xmllint --xinclude --postvalid --noout osmobsc-vty-reference.xml
dblatex  -P draft.mode=no osmobsc-vty-reference.xml
Build the book set list...
Build the listings...

http://docbook.org/xml/5.0/dtd/docbook.dtd:1792: parser error : ATTLIST: no name for Attribute
<!ATTLIST locator
                 ^
unable to parse /home/osmocom-build/jenkins/workspace/osmo-gsm-manuals/OsmoBSC/osmobsc-vty-reference.xml

Unexpected error occured
Error: xsltproc failed
../build/Makefile.docbook.inc:34: recipe for target 'osmobsc-vty-reference.pdf' failed
make[1]: *** [osmobsc-vty-reference.pdf] Error 1
make[1]: Leaving directory '/home/osmocom-build/jenkins/workspace/osmo-gsm-manuals/OsmoBSC'

History

#1 Updated by neels 7 months ago

  • Subject changed from osmo-gsm-manuals master branch build is broken with "arser error : ATTLIST: no name for Attribute" to osmo-gsm-manuals master branch build is broken with "parser error : ATTLIST: no name for Attribute"

#2 Updated by neels 7 months ago

  • Status changed from New to In Progress
  • Assignee set to neels

I can reproduce the failure when building on Osmobuild1, however, it sporadically happens in different subdirs and running 'make' again after the failure finishes the build successfully. Maybe it is related to concurrency or unsynced file system??

#3 Updated by neels 7 months ago

and all of a sudden the problem no longer reproduces ... will leave it open for a few days

#4 Updated by neels 5 months ago

  • Status changed from In Progress to Rejected

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)