With 2.24.1:

Making all in tests
make[3]: entrant dans le répertoire « /var/tmp/portage/gnome-base/gnome-keyring-2.24.1/work/gnome-keyring-2.24.1/pam/tests »
sh ../../tests/prep-tests.sh -b run-auto-test
sh ../../tests/prep-tests.sh -b run-prompt-test unit-test-pam-setup.c unit-test-pam.c
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../daemon -I../.. -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12   -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include      -DEXTERNAL_TEST -O2 -march=native -pipe -g -MT run_prompt_test-unit-test-pam-setup.o -MD -MP -MF .deps/run_prompt_test-unit-test-pam-setup.Tpo -c -o run_prompt_test-unit-test-pam-setup.o `test -f 'unit-test-pam-setup.c' || echo './'`unit-test-pam-setup.c
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../daemon -I../.. -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12   -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include      -DEXTERNAL_TEST -O2 -march=native -pipe -g -MT run_prompt_test-unit-test-pam.o -MD -MP -MF .deps/run_prompt_test-unit-test-pam.Tpo -c -o run_prompt_test-unit-test-pam.o `test -f 'unit-test-pam.c' || echo './'`unit-test-pam.c
unit-test-pam.c:48: erreur: expected ‘)’ before ‘*’ token
unit-test-pam.c:68: erreur: expected ‘)’ before ‘*’ token
unit-test-pam.c:81: erreur: expected ‘)’ before ‘*’ token
make[3]: *** [run_prompt_test-unit-test-pam.o] Erreur 1
make[3]: *** Attente des tâches non terminées....
unit-test-pam-setup.c: In function ‘conv_func’:
unit-test-pam-setup.c:59: erreur: expected expression before ‘struct’
unit-test-pam-setup.c:59: attention : assignment makes pointer from integer without a cast
unit-test-pam-setup.c: In function ‘unit_setup_pam’:
unit-test-pam-setup.c:117: attention : non concordance entre pointeur et entier dans une expression conditionnelle (mismatch between a pointer and an integer in a conditional expression)
make[3]: *** [run_prompt_test-unit-test-pam-setup.o] Erreur 1
make[3]: quittant le répertoire « /var/tmp/portage/gnome-base/gnome-keyring-2.24.1/work/gnome-keyring-2.24.1/pam/tests »
make[2]: *** [all-recursive] Erreur 1
make[2]: quittant le répertoire « /var/tmp/portage/gnome-base/gnome-keyring-2.24.1/work/gnome-keyring-2.24.1/pam »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /var/tmp/portage/gnome-base/gnome-keyring-2.24.1/work/gnome-keyring-2.24.1 »
make: *** [all] Erreur 2

Thanks for bringing this up. Is this still the case? If so, what is the output of the following command on your machine:

ulimit -a

Created attachment 138748 [details]
build+test.log

# ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 16103
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited


Also with gnome-keyring 2.26.3, the test that is failing is different. I think this is related to initialization of the socket but I haven't got a clue yet of how to fix it. This also breaks doc generation here but this is a side issue that can be looked up later.

Actually re-reading our downstream bug about doc generation failure, it looks like gtk-doc fails because it also cannot initialize the lib correctly.

[snip]
/usr/lib/libICE.so /usr/lib/libXi.so /usr/lib/libXext.so -lpthread
/usr/lib/libglitz.so /usr/lib/libpng12.so /usr/lib/libxcb-render-util.so
/usr/lib/libxcb-render.so /usr/lib/libXrender.so /usr/lib/libX11.so
/usr/lib/libxcb.so /usr/lib/libXau.so /usr/lib/libXdmcp.so
/usr/lib/libpango-1.0.so -lm /usr/lib/libfontconfig.so /usr/lib/libfreetype.so
-lz /usr/lib/libexpat.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so
-ldl /usr/lib/libglib-2.0.so -pthread
gtk-doc: Running scanner gcr-scan
gcr-scan: gck-rpc-module.c:228: call_connect: Assertion `pkcs11_socket_path[0]'
failed.
Scan failed: 
make[4]: *** [scan-build.stamp] Ошибка 255

https://bugs.gentoo.org/show_bug.cgi?id=267957

Created attachment 138749 [details]
run-auto-test-rapport-anomalie.txt

Here is a full backtrace of what happens when the test fails.

If it helps, I noticed that it installs fine if I remove gnome-keyring first (tried this twice now). However, if I then try to "remerge" it without removing it first it fails on the same error again

Thanks Gilles. Removed that assertion. The condition is now better handled by the actual error messages.

thanks, that fixes the issue after two builds (see bug #595100 if that sounds odd to you ;))