Created attachment 556288 [details] build.log FAIL: test-data-der 18 /gkm/data-der/write_pkcs8_encrypted ERROR: test-data-der process failed: 250 FAIL: test-gnome2-private-key 2 /gnome2-store/private-key/save ERROR: test-gnome2-private-key process failed: 250 ============================================================================ Testsuite summary for gnome-keyring 3.28.2 ============================================================================ # TOTAL: 641 # PASS: 627 # SKIP: 10 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 2 Same tests fail on stable gnome-keyring-3.20.1, so at least it's no regression.
Created attachment 556290 [details] test-suite.log
Created attachment 556292 [details] emerge --info
I once hit the test-data-der test failure, though the details looked different. Looks to be a race issue, that maybe 3.31.91-r1 improves on. Not sure what the other one is about.
Created attachment 592264 [details] build.log (3.31.91-r1) Nope, 3.31.91-r1 does not improve the situation.
Seeing both failure during gnome-keyring-3.36.0 stabilization on x86: [...] # DEBUG: generalTime generalTime: decoded tag did not match expected # DEBUG: generalTime generalTime: decoded tag did not match expected # DEBUG: DSAPrivateKey DSAPrivateKey: decoded tag did not match expected # DEBUG: implicitlyCA implicitlyCA: decoded tag did not match expected ok 17 /gkm/data-der/write_pkcs8_plain # DEBUG: generalTime generalTime: decoded tag did not match expected # DEBUG: generalTime generalTime: decoded tag did not match expected # DEBUG: generalTime generalTime: decoded tag did not match expected # DEBUG: generalTime generalTime: decoded tag did not match expected Bail out! ERROR:pkcs11/gkm/test-data-der.c:639:test_write_pkcs8_encrypted: assertion failed: (res == GKM_DATA_SUCCESS) ** ERROR:pkcs11/gkm/test-data-der.c:639:test_write_pkcs8_encrypted: assertion failed: (res == GKM_DATA_SUCCESS) and ERROR: test-gnome2-private-key ============================== # ./build/tap-driver --test-name test-gnome2-private-key --log-file test-gnome2-private-key.log --trs-file test-gnome2-private-key.trs --color-tests yes --enable-hard-errors yes --expect-failure no --format=tap -- sh -c exec "$0" "$@" --tap ./test-gnome2-private-key # random seed: R02S417ccfc9265748d1c6cc6324ed4d4b4e 1..2 # Start of gnome2-store tests # Start of private-key tests ok 1 /gnome2-store/private-key/load Bail out! ERROR:pkcs11/gnome2-store/test-gnome2-private-key.c:147:test_save_private_key: assertion failed: (gkm_data_der_read_private_pkcs8_crypted (data, "booo", 4, &sexp) == GKM_DATA_SUCCESS) ** ERROR:pkcs11/gnome2-store/test-gnome2-private-key.c:147:test_save_private_key: assertion failed: (gkm_data_der_read_private_pkcs8_crypted (data, "booo", 4, &sexp) == GKM_DATA_SUCCESS)
please retry with gnome-keyring-3.36.0-r1
Created attachment 667241 [details] build.log (3.36.0, ppc) Seems the same 2 tests fail but are only rated as error now, not as failure. [...] ERROR: test-data-der process failed: -6 ERROR:pkcs11/gnome2-store/test-gnome2-private-key.c:147:test_save_private_key: assertion failed: (gkm_data_der_read_private_pkcs8_crypted (data, "booo", 4, &sexp) == GKM_DATA_SUCCESS) ERROR: test-gnome2-private-key process failed: -6 ============================================================================ Testsuite summary for gnome-keyring 3.36.0 ============================================================================ # TOTAL: 643 # PASS: 629 # SKIP: 12 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2
Created attachment 667244 [details] emerge --info
Created attachment 667247 [details] test-suite.log (3.36.0, ppc)
Same on x86 still w/ 42.1.