Skip to the navigation links
Last modified: 21 September 2010

URL: http://cxc.harvard.edu/ciao4.2/bugs/smoketests.html

Bugs: Smoke Tests


A list of bugs fixed in CIAO 4.2 is available.


Bugs

ChIPS

  1. Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so:
    cannot open shared object file: No such file or directory
    OR
    Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so:
    cannot open shared object file: no such file or directory
    OR
    Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks" (16 Apr 2010)

  2. (26 Jul 2010)

  3. libGL warning: 3D driver claims to not support visual 0x4b (15 Dec 2008)

  4. CIAO is installed as root and the Chips/GUI smoke tests fail (16 Apr 2010)

  5. ChIPS smoke test comparison fails due to comma in place of decimal point (02 Apr 2010)

Sherpa

  1. Sherpa: "ERROR: test_image (sherpa.image.tests.test_image.test_image)" (13 Jul 2010)

Prism

  1. Segmentation fault prism (18 Feb 2010)

  2. CIAO is installed as root and the Chips/GUI smoke tests fail (16 Apr 2010)

ObsVis

  1. ObsVis tests are skipped if there is no internet connection (15 Dec 2009)

  2. ObsVis requires ds9 v5.7 or higher (15 Dec 2009)


Bugs

ChIPS

  1. Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so:
    cannot open shared object file: No such file or directory
    OR
    Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so:
    cannot open shared object file: no such file or directory
    OR
    Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks" (16 Apr 2010)

    The warning is cosmetic and doesn't impact how ChIPS works. It does, however, cause all the ChIPS smoke tests to fail, e.g.:

    Running test chips-smoke001
    chips-smoke001 FAILED
      Review /tmp/smoke.user/chips-smoke001/diff.log for details
    make[1]: *** [test-chips-smoke001] Error 1
    

    Examining the diff.log files will show that the warning message is the only difference:

    % cat /tmp/smoke.user/chips-smoke001/diff.log
    3d2
    < Gtk-Message: Failed to load module "gnomebreakpad": 
    libgnomebreakpad.so: cannot open shared object file: No such file or 
    directory
    3d2
    

    Workaround:

    The gnome session sets GTK_MODULES to load some debugging tools. If the user simply unsets the GTK_MODULES environment variable, then the warning messages will disappear:

    unsetenv GTK_MODULES
    
  2. (26 Jul 2010)

    The messages may be accompanied by a traceback error:

    Traceback (most recent call last):
      File "/tmp/smoke.al/chips-smoke001/chips-smoke001.py", line 2, in <module>
        strip_chart(3)
      File "/usr/ciao-4.2/lib/python2.6/site-packages/pychips/extensions.py", line 3436, in strip_chart
        __pychips_base__.grid_objects(1, entries,0, gaps,1)
      File "/usr/ciao-4.2/lib/python2.6/site-packages/pychips/pychips_base.py", line 935, in grid_objects
        return _pychips.ChipsRemoteMod_grid_objects(*args)
    RuntimeError: chips ERROR: No current window to perform operation on
    

    Workaround:

    • This error may indicate that the necessary graphics drivers are not installed on the machine running CIAO. For example, if you have a Nvidia graphics card and are running the 32-bit version of CIAO, you must have the 32-bit Nvidia drivers installed.

    • If you have SSH-ed into another machine to run CIAO, be sure that the -X or -Y (or both: "ssh -XY") options were used to enable X11 forwarding. If that doesn't resolve the issue, set

      setenv LIBGL_ALWAYS_INDIRECT 1
      

      This should happen by default when logging into a remote machine, but occasionally the system needs it set explicitly.

    If this information does not resolve the problem, contact Helpdesk for additional diagnostic help.

  3. libGL warning: 3D driver claims to not support visual 0x4b (15 Dec 2008)

    All chips smoke tests may fail due to this warning produced by some ATI graphics cards. The warning is benign and can be ignored.

  4. CIAO is installed as root and the Chips/GUI smoke tests fail (16 Apr 2010)

    The ChIPS and the GUI applications, such as prism and obsvis, open windows as part of running the smoke tests. Often the root account is not allowed to open a window on the machine, which causes these tests to fail.

    The path to diff.log indicates this test was run as the root user:

    /tmp/smoke.root/prism-smoke001/diff.log 
    

    It is is strongly suggested that CIAO be installed as a non-privileged user and not as the root user. If CIAO must be installed in a directory owned by root and you are following the manual process, then

    1. unpack CIAO as root (so creating the ciao-<ver>/ directory);
    2. use the chown utility to change ownership of this directory to the installer's username.
  5. ChIPS smoke test comparison fails due to comma in place of decimal point (02 Apr 2010)

    Some system languages (e.g. Italian) use a comma in place of decimal point by default. This will cause the ChIPS smoke test comparison to fail, because the file packaged with CIAO uses decimal points:

    unix% cat /tmp/smoke.user/chips-smoke001/diff.log
    5c5
    <     Plot [plot1]   (0,15,0,65)  .. (0,90,0,90)
    ---
    >     Plot [plot1]   (0.15,0.65)  .. (0.90,0.90)
    11c11
    <     Plot [plot2]   (0,15,0,40)  .. (0,90,0,65)
    ---
    >     Plot [plot2]   (0.15,0.40)  .. (0.90,0.65)
    20c20
    <     Plot [plot3]   (0,15,0,15)  .. (0,90,0,40)
    ---
    >     Plot [plot3]   (0.15,0.15)  .. (0.90,0.40)
    

    If the decimal point/comma difference is the only thing recorded in the log file, ChIPS is fine to use.

Sherpa

  1. Sherpa: "ERROR: test_image (sherpa.image.tests.test_image.test_image)" (13 Jul 2010)

    The Sherpa smoke test fails and the log contains these errors:

    ERROR: test_image (sherpa.image.tests.test_image.test_image)
    ----------------------------------------------------------------------
    Traceback (most recent call last):
    ValueError: total size of new array must be unchanged
    

    This is an intermittent error in the code that Sherpa uses to talk with DS9 via XPA. Run the smoke tests a second time and the errors should go away. If they do not, contact Helpdesk for further assistance.

Prism

  1. Segmentation fault prism (18 Feb 2010)

    The prism smoke tests will segmentation fault if there are incompatible .fontconfig files cached on the user's system. Try renaming (or removing) the .fontconfig cache:

    unix% mv ~/.fontconfig ~/.fontconfig_orig
    

    If this does not fix the prism problem, contact Helpdesk.

  2. CIAO is installed as root and the Chips/GUI smoke tests fail (16 Apr 2010)

    The ChIPS and the GUI applications, such as prism and obsvis, open windows as part of running the smoke tests. Often the root account is not allowed to open a window on the machine, which causes these tests to fail.

    The path to diff.log indicates this test was run as the root user:

    /tmp/smoke.root/prism-smoke001/diff.log 
    

    It is is strongly suggested that CIAO be installed as a non-privileged user and not as the root user. If CIAO must be installed in a directory owned by root and you are following the manual process, then

    1. unpack CIAO as root (so creating the ciao-<ver>/ directory);
    2. use the chown utility to change ownership of this directory to the installer's username.

ObsVis

  1. ObsVis tests are skipped if there is no internet connection (15 Dec 2009)

    The ObsVis smoke tests will be skipped when no connection to the internet is found. To ensure ObsVis is installed properly, connect to the internet before running the smoke tests. The smoke test suite will not fail if the ObsVis tests are skipped for this reason.

  2. ObsVis requires ds9 v5.7 or higher (15 Dec 2009)

    If a version of ds9 older than 5.7 is referred to in the .ciaorc file, the ObsVis smoke tests will fail. This will only occur if the user has changed the ds9 version in the file:

    unix% less ~/.ciaorc
    ...
    # Replace /usr/local/bin with path to ds9 to force use of local ds9
    #DS9 /usr/local/bin
    DS9 /Applications/DS9.app/Contents/MacOS
    

Bugs fixed in CIAO 4.2

The following is a list of bugs that were fixed in the CIAO 4.2 software release.

  1. ObsVis fails because it can't find ds9 (28 Jul 2009)
    (Mac OS X 10.4 only)

    The obsvis tool checks what OS is being used and sets the ds9 path based on the answer. There is a bug in how this is done on OS X 10.4 (Tiger) machines. The ObsVis smoke tests will fail with a message like:

    dyld: Library not loaded: /usr/lib/libiconv.2.dylib
    Referenced from: /Applications/ciao-4.1/ots/bin/ds9
    Reason: Incompatible library version: ds9 requires version 7.0.0 or
    later, but libiconv.2.dylib provides version 5.0.0 
    /Applications/ciao-4.1/bin/ds9: line 7: 10825 Trace/BPT trap ${EXE} -
    analysis ${ASCDS_INSTALL}/config/ciao.ds9 "$@"
    

    Workaround:

    1. Download and install the Mac OS X "Application" version of ds9 for Tiger: ds9 OS X Tiger disk image.

    2. In your CIAO installation, make a link to the ds9 Application:

      cd $ASCDS_INSTALL/ots/bin/
      mv ds9 ds9.ciao
      ln -s /path/to/SAOImage\ DS9.app/ds9 .
      

      Be sure to escape the space in the directory name.


Last modified: 21 September 2010