Source: universal-ctags
Version: 0+git20180225-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/universal-ctags.html

...
Summary (see CMDLINE.tmp to reproduce without test harness)
------------------------------------------------------------
  #passed:                                850
  #FIXED:                                 2
        parser-puppetManifest.r/puppet-tag
        parser-puppetManifest.r/puppet-tagged
  #FAILED (broken args.ctags?):           0
  #FAILED (unexpected-exit-status):       0
  #FAILED (unexpected-output):            0
  #TIMED-OUT (10s)                        0
  #skipped (features):                    15
        fq-json
        simple-ctags-aspell
        simple-dbusinspect
        simple-glade
        simple-maven2
        simple-plist
        simple-svg
        parser-ansibleplaybook.r/play-name
        parser-ant.r/regex-based
        parser-ant.r/xpath-based
        parser-fortran.r/common-json.f
        parser-relaxng.r/element
        parser-relaxng.r/grammar
        parser-xslt.r/xslt-simple
        parser-yaml.r/yaml-anchor
  #skipped (languages):                   0
  #known-bugs:                            15
        parser-autoconf.r/nested-block.ac
        parser-c.r/attr-attached-to-array-failed
        parser-c.r/extern_variable.h
        parser-cxx.r/cxx-keywords-as-c-identifiers
        parser-cxx.r/cxx-keywords-as-c-identifiers
        parser-cxx.r/namespace-and-scope
        parser-cxx.r/variables-prototypes.cpp
        parser-itcl.r/fq-with-namespace
        parser-java.r/bug1777344.java
        parser-javascript.r/js-scope-resolution
        parser-m4.r/m4-quotestring
        parser-puppetManifest.r/puppet-virtualresources
        parser-python.r/newlines-cr
        parser-scheme.r/scheme-srfi-30-comment
        parser-scheme.r/scheme-string
make[1]: Leaving directory '/build/1st/universal-ctags-0+git20180225'
dh_auto_test: make V=1 -j16 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:10: build] Error 2

Reply via email to