On 21/10/13 15:54, Michael Biebl wrote: > Source: pango1.0 > Version: 1.36.0-1 > Severity: serious > User: debian-...@lists.debian.org > > pango1.0 FTBFS on kfreebsd-i386 when executing the test-suite: > > /«PKGBUILDDIR»/./test-driver: line 95: 41714 Trace/breakpoint trap "$@" > > $log_file 2>&1 > FAIL: test-pangocairo-threads
The test is failing with (process:7450): GLib-ERROR **: creating thread '37': Error creating thread: Resource temporarily unavailable The test is trying to create 100 threads, but pthread_create returns EAGAIN because it hits some limit, which makes g_thread_new() abort (as stated in the docs, g_thread_try_new() wouldn't abort but return NULL). The question is, why are we hitting the limit so soon here? ulimit on fischer (where I'm debugging this) reports: max user processes (-u) 5547 so I doubt we're hitting the maximum number of threads here. Perhaps the test should use g_thread_try_new() and retry a limited number of times on EAGAIN. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
