Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#595 test suite failure with current wxWindows

closed-works-for-me
nobody
Other (155)
5
2007-11-14
2007-10-30
No

Linux

Gnuplot 4.2.2
wxGTK 2.6.4.0

See build log for details and http://bugs.gentoo.org/show_bug.cgi?id=197417 for reference.

Discussion

  • build log file

     
    Attachments
  • Ethan Merritt
    Ethan Merritt
    2007-10-30

    Logged In: YES
    user_id=235620
    Originator: NO

    I see two problems indicated in the build log, followed eventually by a floating point exception.

    The first set of warnings is from the vgagl terminal driver. It is probably harmless, but that whole driver is a bit suspect these days because it depends on the external library libsvgalib, which has been problematic for a long time.

    The second set of warnings is triggered by a number of the demos, and can be recognized by lines like:
    line 124: warning: Warning - difficulty fitting plot titles into key
    This indicates a font problem. Either the environment is providing no default font at all, or the default font is unreasonably large compared to the plot size.

    Not enough info is present to pin down the floating point error. It is possible, though not very likely, that this is also a side-effect of the bad font size. Could you try to reproduce the problem using a non-interactive terminal?

     
  • Logged In: YES
    user_id=21956
    Originator: YES

    Do you mean non-xterm-alike with non-interactive?

     
  • Ethan Merritt
    Ethan Merritt
    2007-10-31

    Logged In: YES
    user_id=235620
    Originator: NO

    I don't understand your question.
    I had in mind:
    setenv GNUTERM "postscript solid color"
    make check > check.ps

    That should leave you with a PostScript file containing all the demo output,
    with any error messages on the screen. Most annoyingly the PostScript output in this case contains about 70 lines of output from "make" at the front. I wish I knew how to disable that.

    The point in this case is that postscript generation will never fail due to font issues. If you don't see this same floating overflow, then it must be something specific to wxt rather than to the core gnuplot plotting code. Given the previous font-related errors, that would be where I would start looking, although I can't rule out that it's something else entirely.

     
  • Logged In: YES
    user_id=27517
    Originator: NO

    > 70 lines of output from "make" at the front. I wish I knew how to disable that.

    Easy:

    cd "$gnuplot_build_dir/demo"
    env GNUTERM=postscript \ GNUPLOT_PS_DIR="$gnuplot_srcdir/term/PostScript" \ make -s check

    generates a whopping 530 pages of Postscript output. Passing options "color solid" this way doesn't work, though.

     
  • Logged In: YES
    user_id=21956
    Originator: YES

    I was talking about a terminal emulation. :) Now I got it you talked about a Gnuplot terminal. Anyway, running the steps mentioned by Hans-Bernhard, I get a 512 page PostScript file which looks sane and no failure for the make check run. You surely don't want a 15MB file as attachment...

     
  • Ethan Merritt
    Ethan Merritt
    2007-11-13

    Logged In: YES
    user_id=235620
    Originator: NO

    Fine. So there is no error when you run "make check" with PostScript output. Then it must be terminal-specific, rather than a failure in some core routine.

    If you can narrow down the failure to a specific plot command on a specific terminal (wxt in this case), then we can try to fix it. Although I'm still guessing that it's a font problem, so it may not be easily reproducible on a different machine.

    Other than that, all I can say is that both 4.2.2 and current CVS build and pass the "make check" test just fine here using the wxt terminal on several different machines and library versions.

     
    • status: open --> open-works-for-me
     
  • Logged In: YES
    user_id=21956
    Originator: YES

    Sorry, no time to debug this with too much effort. On our side I disabled the test suite when wxwindows is enabled, maybe the user who reported the problem will go deeper.

     
  • Ethan Merritt
    Ethan Merritt
    2007-11-14

    Logged In: YES
    user_id=235620
    Originator: NO

    OK.
    I'll close this report, but please go ahead and open a new one if there is a more specific failure scenario.

     
  • Ethan Merritt
    Ethan Merritt
    2007-11-14

    • status: open-works-for-me --> closed-works-for-me