GNOME Bugzilla – Bug 540385
doesn't pass "make check"
Last modified: 2009-03-15 22:14:26 UTC
as seen in rb-0.11.5 and reported on the ml, rb doesn't pass make check on many machines I have. Please also look at our downstream bug report (ignoring the part about unavailable X server that is easily fixable on our side) at https://bugs.gentoo.org/show_bug.cgi?id=216146 Attaching the trace in a moment.
Created attachment 113491 [details] errors.log log of "make check"
works fine for me.
what is this error about, do I need something special to make those message go away ? I have check (the framework) and Xvfb what else do I need ? test-rhythmdb: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. What about test.ogg, is it if the test if failing ? I've reproduced the exact same problem on 4 different machines both on amd64 and x86 and the gentoo bug tells me there is more people out there that experience the same problem. I hope I just missed something...
I have no idea what that error is about, but at a guess I'd say it means the x server you're using is broken. I seem to be able to run the tests with xvfb (and my real x server) on my debian sid system with no problems. None of the filenames used in the tests need to exist.
I thought I would give at shot at current svn trunk head before any release comes out so we can hopefully get it fixed. Things looks a bit brighter since only one test is still failing. Here is the output: (gdb) run Starting program: /home/eva/devel/svn/gnome/rhythmbox/tests/test-rhythmdb-property-model [Thread debugging using libthread_db enabled] [New Thread 0x2b9f1aba6130 (LWP 24735)] (22:58:12) [0x649040] [rb_debug_init_match] rb-debug.c:215: Debugging enabled Running suite(s): rhythmdb-property-model >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df040 chaining to base model (nil) (22:58:12) [0x649040] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry added (22:58:12) [0x649040] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry added ---------------------------------------------------------------- (22:58:12) [0x649040] [rhythmdb_query_model_add_entry] rhythmdb-query-model.c:1122: inserting entry 0x6e08d0 at index -1 (22:58:12) [0x649040] [idle_process_update] rhythmdb-query-model.c:1088: inserting row at index -1 (22:58:12) [0x649040] [rhythmdb_property_model_insert] rhythmdb-property-model.c:661: adding new property "x" (22:58:12) [0x649040] [mark_signal] test-utils.c:96: got signal 'row-inserted' (22:58:12) [0x649040] [wait_for_signal] test-utils.c:121: no need to wait for signal 'row-inserted', already received (22:58:12) [0x649040] [rhythmdb_query_model_add_entry] rhythmdb-query-model.c:1122: inserting entry 0x6e0b80 at index -1 (22:58:12) [0x649040] [idle_process_update] rhythmdb-query-model.c:1088: inserting row at index -1 (22:58:12) [0x649040] [rhythmdb_property_model_insert] rhythmdb-property-model.c:661: adding new property "y" (22:58:12) [0x649040] [mark_signal] test-utils.c:96: got signal 'row-inserted' (22:58:12) [0x649040] [wait_for_signal] test-utils.c:121: no need to wait for signal 'row-inserted', already received ---------------------------------------------------------------- (22:58:12) [0x649040] [wait_for_signal] test-utils.c:117: waiting for signal 'row-deleted' (22:58:12) [0x649040] [rhythmdb_property_model_delete_prop] rhythmdb-property-model.c:713: deleting "x": refcount: 1 (22:58:12) [0x649040] [mark_signal] test-utils.c:96: got signal 'row-deleted' (22:58:12) [0x649040] [rhythmdb_property_model_insert] rhythmdb-property-model.c:652: adding "y": refcount 2 ---------------------------------------------------------------- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df040 chaining to base model (nil) (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df100 chaining to base model (nil) ---------------------------------------------------------------- (22:58:12) [0x649040] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry added (22:58:12) [0x649040] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry added (22:58:12) [0x649040] [wait_for_signal] test-utils.c:117: waiting for signal 'entry_added' (22:58:12) [0x649040] [mark_signal] test-utils.c:96: got signal 'entry_added' (22:58:12) [0x649040] [rhythmdb_property_model_insert] rhythmdb-property-model.c:661: adding new property "x" test-rhythmdb-property-model: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df040 chaining to base model (nil) (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df100 chaining to base model (nil) (22:58:12) [0x649040] [rhythmdb_query_model_chain] rhythmdb-query-model.c:784: query model 0x6df100 chaining to base model 0x6df040 (22:58:12) [0x649040] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry added (22:58:12) [0x649040] [wait_for_signal] test-utils.c:117: waiting for signal 'entry_added' (22:58:12) [0x649040] [mark_signal] test-utils.c:96: got signal 'entry_added' test-rhythmdb-property-model: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. 0%: Checks: 3, Failures: 1, Errors: 2 test-rhythmdb-property-model.c:115:F:rhythmdb-property-model-core:test_rhythmdb_property_model_static:0: Assertion '_get_property_count (propmodel, "y") == 1' failed test-rhythmdb-property-model.c:190:E:rhythmdb-property-model-core:test_rhythmdb_property_model_query:0: (after this point) Early exit with return value 1 test-rhythmdb-property-model.c:320:E:rhythmdb-property-model-core:test_rhythmdb_property_model_query_chain:0: (after this point) Early exit with return value 1 Program exited with code 03. I'll keep trying to find the cause of these IO error as time permits but I hope you will have some inspiration before me.
pretty sure this fixes it: 2009-03-11 Jonathan Matthew <jonathan@d14n.org> * tests/test-rhythmdb-property-model.c: (START_TEST), (main): Need to use wait_for_signal for some of the property model tests now, since rhythmdb emits entry-changed signals in an idle handler. Use the common setup stuff the other test suites use for calling gtk_init in the child process (if forking). Should fix #540385.
just svn up'ed to double check and the test suite now runs fine. Thanks for fixing it.