Set Sandbox up as a working slave

[wd15]

Sandbox is having issues. Under buildbot the modules tests crash during the VTK tests in the following way:

import fipy.viewers.vtkViewer.test ... ok
import fipy.viewers.tsvViewer ... ok
import fipy.viewers.vtkViewer.vtkCellViewer ... ok
import fipy.viewers.vtkViewer.vtkFaceViewer ... ok
_test (fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer)
Doctest: fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer._test ... 
(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

(process:1414): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

(process:1414): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

(process:1414): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed

(process:1414): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(process:1414): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(process:1414): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()

command timed out: 1200 seconds without output, killing pid 1414
process killed by signal 9
program finished with exit code -1
elapsedTime=1295.846156

When I simply run the tests as wd15 on sandbox, the VTK tests fail, but not in a devastating way.

======================================================================
FAIL: Doctest: fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer._test
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.6/doctest.py", line 2163, in runTest
raise self.failureException(self.format_failure(new.getvalue()))
AssertionError: Failed doctest test for fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer._test
  File "/home/wd15/Documents/python/fipy/trunk/fipy/viewers/vtkViewer/vtkCellViewer.py", line 59, in _test

----------------------------------------------------------------------
File "/home/wd15/Documents/python/fipy/trunk/fipy/viewers/vtkViewer/vtkCellViewer.py", line 66, in fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer._test
Failed example:
from enthought.mayavi.sources.vtk_file_reader import VTKFileReader
Exception raised:
Traceback (most recent call last):
File "/usr/lib/python2.6/doctest.py", line 1253, in __run
compileflags, 1) in test.globs
File "<doctest fipy.viewers.vtkViewer.vtkCellViewer.VTKCellViewer._test[4]>", line 1, in <module>
from enthought.mayavi.sources.vtk_file_reader import VTKFileReader
ImportError: No module named mayavi.sources.vtk_file_reader

Fist thing is to try and figure out why they are failing in different ways. It could be that the environment is slightly different under buildbot then when I am logged in. I'm going to try and debug this. Some ideas:

• Uninstall and install mayavi again. Just in case.

• Check the environment and the .bashrc file and see that the LD_LIBRARY_PATH is the same and other variables.

  Imported from trac ticket #337, created by wd15 on 04-27-2011 at 12:25, last modified: 01-10-2012 at 11:50

[wd15]

It might be more worthwhile now trying to get the test to pass when it isn't running as a cronjob.

Trac comment by wd15 on 09-12-2011 at 17:45

[wd15]

To get sandbox working correctly required setting the environment variables on the first line of the crontab (which I wasn't aware of previously). The tests now perform identically whether running at a terminal or under buildbot.

Trac comment by wd15 on 01-10-2012 at 11:50