Re: [lmi] [PATCH] Add --gui_test_path command line option to the GUI test.

[Greg Chicares]

On 12/15/2014 03:56 PM, Vadim Zeitlin wrote:
> On Mon, 15 Dec 2014 15:40:20 +0000 Greg Chicares <address@hidden> wrote:
> 
> GC> I'm thinking of the new developer who downloads the sources, builds the
> GC> code, and runs the tests--without any /opt/lmi/gui_test/ directory, and
> GC> without the (potentially proprietary) test files it contains. In that 
> case,
> GC> I'd like the other tests to run smoothly, without any scary messagebox.
> GC> Could you therefore change the messagebox to a reassuring text message on
> GC> stdout? Let's say:
> GC> 
> GC> << "Optional extra tests would be run if any were found in '"
> GC> << test_files_path_.native_file_string()
> GC> << ", but no such directory exists. Proceeding to run built-in tests."
> 
>  This can be done easily, of course, but this message wouldn't be totally
> correct, at least not right now. If the code remains otherwise unchanged,
> we'd simply use the current working directory instead of /opt/lmi/gui_test
> and look in this directory for the miscellaneous input files and if they
> are really not there the tests would fail instead of just not being run.
> 
>  Granted, this will probably change soon as at least InputSequences.cns and
> PasteCensus.cns will disappear completely. I'm not sure about the remaining
> ones though: will CoiMultiplier.cns, MonthlyTrace.ill and MecTesting.mec be
> not needed neither any longer? If so, I prefer to update the code using all
> these files first and then just make the change proposed above.
> 
>  Otherwise, i.e. if we are still going to have any tests requiring files in
> this directory, it would arguably be better to skip them if this directory
> doesn't exist or the required file is not found in it. I.e. I'm thinking of
> making get_test_file_path_for() throw test_skipped_exception if the file is
> not found. Do you think this would be [more] useful?

Having just built lmi on debian, I figured this was the perfect time to
return to this old email that I had marked for followup: I haven't put
any of the proprietary test files here, so...

I've rebuilt wx, even though it's still using gtk+-2; this works fine:

/opt/lmi/build[0]$LD_LIBRARY_PATH=/usr/local/lib:/opt/lmi/local/lib ./lmi_wx 
--ash_nazg

However, the GUI test doesn't work, presumably due to the special way
it starts up (this is wx-3.1 git HEAD as of this morning, BTW):

/opt/lmi/build[0]$LD_LIBRARY_PATH=/usr/local/lib:/opt/lmi/local/lib ./wx_test 
--ash_nazg

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()

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

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()

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

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()

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

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

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

(process:5081): GLib-GObject-CRITICAL **: 
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to 
call g_type_init()
^C
/opt/lmi/build[130]$