This test incorrectly expects the libpurple search path to initially contain exactly one element. Remove this incorrect assertion. --- telegram-purple-1.3.1-checkout/test/loadtest.c 2018-10-27 16:25:06.258459600 +0200 +++ telegram-purple-1.3.1-checkout/test/loadtest.c 2018-10-27 16:25:11.830434770 +0200 @@ -156,7 +156,7 @@ static void tdf_inject_plugin (void) { printf ("Injecting our module into purple_plugins_* ...\n"); purple_plugins_init (); GList *search_paths = purple_plugins_get_search_paths (); - assert (!search_paths->prev && !search_paths->next && search_paths->data); + assert (!search_paths->prev && search_paths->data); GList *new_paths = g_list_append (search_paths, g_strdup ("bin/")); assert (new_paths == search_paths); // Load "my" path before the default. cripts'>koszko-scripts Wojtek's customized Guix
aboutsummaryrefslogtreecommitdiff
path: root/gnu/packages/python.scm
AgeCommit message (Expand)Author
2023-07-20gnu: python: Support native build on the Hurd....Running "test_concurrent_futures" and "test_venv" freeze the Hurd. Tests "test_multiprocessing_forkserver" and "test_multiprocessing_spawn" run over 10mins. Debian simply skips all tests on the Hurd. * gnu/packages/python.scm (python-3.10)[arguments]: When building for the Hurd, add hanging and failing to #:make-flags's --exclude flag. Also, add 'disable-multi-processing' phase to avoid compileall.py hang during install. Janneke Nieuwenhuizen
2023-06-17gnu: Use target-hurd?, system-hurd? instead of hurd-target?, hurd-system?....* gnu/packages/hurd.scm (hurd-target?): Remove. (hurd-system?): Move to... * guix/utils.scm (system-hurd?): ...here. * gnu/packages/*: Update all users, removing (gnu packages hurd) include where now unused. Janneke Nieuwenhuizen