Several tests in the automake-1.11.1 test suite fail. There is a common factor that all of them seem to fail because a call to texi2dvi exits with 1 as the error code instead of 0. Placing the same source files in my home directory and manually running texi2dvi on them, I end up with the same issue there so it does not seem to be related to sandbox or ebuild environment. Failing tests are: instdir-texi.test txinfo3.test txinfo13.test txinfo16.test txinfo18.test txinfo21.test txinfo22.test txinfo23.test txinfo24.test txinfo25.test txinfo28.test txinfo33.test version7.test Reproducible: Always Steps to Reproduce: 1. Merge automake with FEATURES="test" Actual Results: 13 tests fail Expected Results: All tests pass Bug 228205 looked related if not a duplicate but not enough information and context is given there to determine that. This version of automake is also not listed there.
Created attachment 255627 [details] log of version7 test
Created attachment 255629 [details] Log of txinfo33 test
Created attachment 255631 [details] Log of txinfo28 test
Created attachment 255633 [details] Log of txinfo25 test
Created attachment 255635 [details] Log of txinfo24 test
Created attachment 255637 [details] Log of txinfo23 test
Created attachment 255639 [details] Log of txinfo22 test
Created attachment 255641 [details] Log of txinfo21 test
Created attachment 255643 [details] Log of txinfo18 test
Created attachment 255645 [details] Log of txinfo16 test
Created attachment 255647 [details] Log of txinfo13 test
Created attachment 255649 [details] Log of txinfo3 test
Created attachment 255651 [details] Log of instdir-texi test
you don't have texlive-texinfo installed, right ? ebuilds need to depend on virtual/texi2dvi for using texi2dvi, which is not the case of automake. FWIW: I don't have such tests failures here.
(In reply to comment #14) > you don't have texlive-texinfo installed, right ? > > ebuilds need to depend on virtual/texi2dvi for using texi2dvi, which is not the > case of automake. > FWIW: I don't have such tests failures here. > I did not have texlive-texinfo installed. It was insufficient for passing the tests too. With virtual/texi2dvi, the tests did pass. Since texinfo is where the texi2dvi executable comes from and for texi2dvi to work, it needs the virtual/texi2dvi stuff, does that indicate that's the root issue? texinfo is missing runtime dependency on virtual/texi2dvi?
I recall we discussed this years ago: texinfo is a core package and it seems a bit of an overkill to make it pull in latex stuff unconditionally. It provides the texi2dvi executable but for it to work one needs virtual/texi2dvi and packages using it should depend on it.
is there a way to check for this ? so we could have the tests automatically SKIP when full support isnt available. i'd like something that can be merged upstream, so ebuild checks arent what i'm thinking of.
Texinfo has its tests pass so assuming they have a texi2dvi test, they are skipping it or expecting it to fail somehow. It might be nice to improve the texi2dvi executable to not fail so quietly when the dependencies aren't available too. If you run texi2dvi by hand (It's not just ebuilds that might run it) it just quits with no obvious failure and that's not good.
(In reply to comment #17) > is there a way to check for this ? so we could have the tests automatically > SKIP when full support isnt available. i'd like something that can be merged > upstream, so ebuild checks arent what i'm thinking of. > maybe the return value of "kpsewhich texinfo"
(In reply to comment #19) > (In reply to comment #17) > > is there a way to check for this ? so we could have the tests automatically > > SKIP when full support isnt available. i'd like something that can be merged > > upstream, so ebuild checks arent what i'm thinking of. > > > > maybe the return value of "kpsewhich texinfo" > I remember talking with libcaca's upstream about a case like that years ago, there is now some autoconf foo there for checking that the required latex packages are available. Nothing more to do for tex. CC _me_ back if you need an answer to a question.
