[Octave-bug-tracker] [bug #55225] building doc figures in .eps format occasionally silently fails

[Mike Miller]

URL:
  <https://savannah.gnu.org/bugs/?55225>

                 Summary: building doc figures in .eps format occasionally
silently fails
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Fri 14 Dec 2018 11:27:08 AM PST
                Category: Plotting with OpenGL
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

On my system, building the figures for the user manual in the .eps format
occasionally fails with no error message and no output file produced. The
error only becomes apparent when octave.dvi is built, at which point TeX
complains about the missing include file.

This is reproducible, although not 100% of the time, and is not always the
same figures. The most recent example on my system:


$ rm -f doc/interpreter/*.{dvi,eps,pdf,png}
$ make -j1 V=1 all
…
…/doc/interpreter/poly.texi:838: Could not open file splinefit2.eps,
ignoring it.
…
/usr/bin/texi2dvi: etex exited with bad status, quitting.


And sure enough, the file doc/interpreter/splinefit2.eps is missing. Scrolling
up through the build output, I do see the following command


/bin/bash run-octave --norc --silent --no-history --path …/doc/interpreter/
--eval "splineimages ('doc/interpreter/', 'splinefit2', 'eps');"


With no error or indication that the command failed, simply no output file
produced.

On a second or third repeat of the same sequence, it may work, or there may be
a different set of 1 or 2 images missing.

This is with a real display, Intel integrated graphics, Qt toolkit, Qt 5.11.2,
gl2ps 1.4.0.




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55225>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/