https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-text/pdfgrep-2.1.2 fails tests. Discovered on: amd64 (internal ref: tinderbox) NOTE: This machine uses a clang/LLVM toolchain. If you think that this issue is strictly related to clang/LLVM please block bug 408963. If you think that this issue isstrictly related to the LLD linker, please block bug 731004.
Created attachment 651850 [details] build.log build log and emerge --info
I could reproduce this on my system. Looking at pdfgrep.log shows, for example, for the failing "Context after" test in context.exp, the following pdfgrep output: Running ./pdfgrep.tests/context.exp ... spawn /home/flo/data/code/pdfgrep/src/pdfgrep --color=never -A1 one|five /tmp/pdfgrep_test s.8HVMmpQ1NI/lines.pdf line one line two -- line five line six FAIL: Context after where the expected output is "line one line two -- line five line six" Note that there is only a single space between 'line' and (one|two|five|six). I still need to investigate if the additional whitespace is already in the original PDF create by pdfgrep testsuite, or if it's only in pdfgrep's output.
The pdfgrep developer and I are currently investigating this.
Some rough thoughts: - play with libpcre* use flags - libpcre1 vs libpcre2 if it supports both - try upgrading various libraries in a Debian container - what about in a vanilla Gentoo docker container? reproducible then?
