summaryrefslogtreecommitdiff
path: root/src/run-js-test.c
AgeCommit message (Collapse)AuthorFilesLines
2013-11-26bluetooth: Remove GnomeBluetoothApplet hacksBastien Nocera1-8/+0
https://bugzilla.gnome.org/show_bug.cgi?id=719341
2012-10-17Remove use of deprecated g_type_init () ...Florian Müllner1-1/+0
... and bump GObject requirement accordingly. https://bugzilla.gnome.org/show_bug.cgi?id=686318
2012-06-24run-js-test: GC twice after running a testJasper St. Pierre1-0/+3
When running with Valgrind, this helps us ensure that we're managing memory correctly. We need to GC twice as finalizing an object in the sweep can unroot objects which were already marked. Technically, it could be that we'll need to GC more than twice, but GCing twice should hopefully last us for now. https://bugzilla.gnome.org/show_bug.cgi?id=678737
2011-12-16run-js-test: Do not use the default stageFlorian Müllner1-3/+1
This was left out in commit faff0738eb.
2011-10-18Drop deprecated g_thread_init callJasper St. Pierre1-2/+0
GThread will automatically initialize at program start now. https://bugzilla.gnome.org/show_bug.cgi?id=662011
2011-09-05run-js-test: fixDan Winship1-0/+1
Needs to explicitly initialize the ShellGlobal now https://bugzilla.gnome.org/show_bug.cgi?id=649631
2011-07-27tests: fix up typelib include pathsDan Winship1-2/+9
The js modules have so many imports back and forth that it's pretty much guaranteed that if you import even one of them, you'll end up importing all of them, including ui.status.bluetooth and ui.status.network. So fix up the typelib include paths the same way gnome-shell-jhbuild does, so we can find everything. https://bugzilla.gnome.org/show_bug.cgi?id=650298
2011-05-16environment: move more init stuff here from main.jsDan Winship1-13/+13
Move some more environment-initializationy stuff from main.js to environment.js, and be more careful about not importing shell JS modules until after the environment has been fully patched. Change gnome-shell-plugin to call Environment.init() before Main.start(); this means that Environment.init() now runs before any shell JS modules (besides environment itself) have been imported. Make run-js-test create a ShellGlobal and use its js_context, so that the shell_global_set_property_mutable() stuff in Environment.init() will work correctly in tests as well. https://bugzilla.gnome.org/show_bug.cgi?id=649203
2011-03-13Fix handling of clutter_init() failuresOwen W. Taylor1-1/+1
clutter_init() fails under normal circumstances like being unable to open a display connection, so it shouldn't be handled with g_error() producing a core dump. Clutter consistently produces an error message when clutter_init() fails, so we don't need to print out any error message. https://bugzilla.gnome.org/show_bug.cgi?id=643910
2011-03-13Silence -Werror for other clutter_init callersColin Walters1-1/+2
2010-11-12Add run-js-test executable to run testsOwen W. Taylor1-0/+144
ST makes use of GTK+ for input methods and for icon themes; therefore we have need to initialize GTK+ in order to test these parts of Clutter. Instead of LD_PRELOADING our module, use a separately compiled executable that links to the UI components in GNOME Shell, initializes Clutter and GTK+ and hooks them together. Getting all the symbols from St and the GUI components exported for use via GJS requires a bit of contortion: we need to actually link the St convenience library into a shared library and link the executable to that since there is no way with libtool to take a convenience library and put all its symbols into an executable --whole-archive style. https://bugzilla.gnome.org/show_bug.cgi?id=633657
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-24 13:13:27 +0000