Summary: | =app-text/texlive-core-2015 (and -2014-r4) fails luajiterr test | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonathan Lovelace <kingjon3377> |
Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | jstein, tex |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Compressed build log showing failing test
test-suite log showing details of failing test |
Description
Jonathan Lovelace
2016-04-24 04:45:27 UTC
Created attachment 431758 [details]
test-suite log showing details of failing test
Jonathan, thank you for the report. Can you test, if the problem is fixed in -2015? In my testing, -2015 (with the default USE=luajittex) produces the same failure, with an apparently-identical test-suite.log. With that USE flag disabled (disabling the luajit functionality) the tests pass. However, I just realized that I've made a change in my default CFLAGS between when I last successfully built texlive-core without FEATURES=test-fail-continue (reflected in the final lines of emerge --info above: I tend to treat test failure as compilation failure, and mask test-failing upgrades and live with constant rebuild attempts rather than install demonstrably broken software). The build log (attached above) shows it trying to build with CFLAGS="-fno-unwind-tables -fno-asynchronous-unwind-tables -fomit-frame-pointer". When I disable "-fomit-frame-pointer", the tests build and run successfully again, even on version 2014-r4. Perhaps the ebuild could filter that out of the user's CFLAGS (maybe conditional on USE=luajittex in -2015)? Is this still happening with 2017-r3? seems obsolete. |