Created attachment 554617 [details] build.log =============================== iwd 0.7: ./test-suite.log =============================== # TOTAL: 19 # PASS: 18 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-ssid-to-utf8 ============================ test-ssid-to-utf8: unit/test-ssid-to-utf8.c:73: ssid_to_utf8: Assertion `!memcmp(ssid[i].string, result, strlen(ssid[i].string)) == ssid[i].result' failed. TEST: /util/ssid_to_utf8/ FAIL unit/test-ssid-to-utf8 (exit status: 134)
Created attachment 554619 [details] test-suite.log
Created attachment 554621 [details] emerge --info
Can you check to see if 0.10 has the same failure? Thanks
Created attachment 554629 [details] build.log (iwd-0.10) Yes, 0.10 fails the same test.
I don't have a PPC machine available which has the right kernel configuration to test this myself. Can you try once more with a current kernel and either iwd-9999 or iwd-0.14 so I can have something fresher to ask upstream about? Thanks
My new shiny ppc (G4 MDD) needs to be reassembled first. I will re-run the tests with -9999 and report back the next 1-2 weeks.
Created attachment 566104 [details] build.log (iwd-0.14, kernel 4.20.11) ================================ iwd 0.14: ./test-suite.log ================================ # TOTAL: 18 # PASS: 16 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-eapol ===================== test-eapol: unit/test-eapol.c:2938: eapol_sm_test_tls: Assertion `l_tls_set_auth_data(s->tls, "ell/unit/cert-server.pem", "ell/unit/cert-server-key-pkcs8.pem", NULL)' failed. FAIL unit/test-eapol (exit status: 134) FAIL: unit/test-ssid-to-utf8 ============================ test-ssid-to-utf8: unit/test-ssid-to-utf8.c:73: ssid_to_utf8: Assertion `!memcmp(ssid[i].string, result, strlen(ssid[i].string)) == ssid[i].result' failed. FAIL unit/test-ssid-to-utf8 (exit status: 134)
Created attachment 566106 [details] emerge --info
Thanks for that, can you attach test-suite.log as well?
iwd-9999 shows the same 2 tests failing with the same error messages: FAIL: unit/test-eapol ===================== test-eapol: unit/test-eapol.c:2943: eapol_sm_test_tls: Assertion `l_tls_set_auth_data(s->tls, "ell/unit/cert-server.pem", "ell/unit/cert-server-key-pkcs8.pem", NULL)' failed. FAIL unit/test-eapol (exit status: 134) FAIL: unit/test-ssid-to-utf8 ============================ test-ssid-to-utf8: unit/test-ssid-to-utf8.c:73: ssid_to_utf8: Assertion `!memcmp(ssid[i].string, result, strlen(ssid[i].string)) == ssid[i].result' failed. FAIL unit/test-ssid-to-utf8 (exit status: 134)
Created attachment 566108 [details] test-suite.log (iwd-0.14, kernel 4.20.11)
Created attachment 566110 [details] test-suite.log (iwd-9999, kernel 4.20.11)
Can you try adding -fsigned-char to CFLAGS and see if that helps?
(In reply to Ben Kohler from comment #13) > Can you try adding -fsigned-char to CFLAGS and see if that helps? With -fsigned-char test-ssid-to-utf8 passes. test-eapol still fails.
Can you confirm that your kernel has PKCS8_PRIVATE_KEY_PARSER enabled"? Missing that (or being on <4.20 kernel that lack that support) can cause the eapol test to fail
(In reply to Ben Kohler from comment #15) > Can you confirm that your kernel has PKCS8_PRIVATE_KEY_PARSER enabled"? > Missing that (or being on <4.20 kernel that lack that support) can cause the > eapol test to fail # grep PKCS8 .config CONFIG_PKCS8_PRIVATE_KEY_PARSER=y
Created attachment 566138 [details] kernel .config (4.20.11, PowerMac G4 MDD)
Upstream just added a debug option for this, can you set IWD_TLS_DEBUG=1 in your calling environment, and run tests on 9999 again? Will need to pull fresh from git, the change hit <1hr ago
Ok, now with "IWD_TLS_DEBUG=1 LC_MESSAGES=C FEATURES="test" ACCEPT_KEYWORDS="**" emerge -1 net-wireless/iwd" (still -fsigned-char) I get: FAIL: unit/test-eapol ===================== l_tls_set_auth_data:2590 cert-path=ell/unit/cert-server.pem priv-key-path=ell/unit/cert-server-key-pkcs8.pem priv-key-passphrase=(nil) l_tls_set_auth_data:2606 Error loading ell/unit/cert-server.pem test-eapol: unit/test-eapol.c:2951: eapol_sm_test_tls: Assertion `l_tls_set_auth_data(s->tls, "ell/unit/cert-server.pem", "ell/unit/cert-server-key-pkcs8.pem", NULL)' failed. FAIL unit/test-eapol (exit status: 134)
Created attachment 566144 [details] test-suite.log (iwd-9999, kernel 4.20.11, 'debug', '-fsigned-char')
Ok test-ssid-to-utf8 should be fixed in 0.14-r1 & 9999, still working on test-eapol
Found out this last eapol test is failing because the bundled ell isn't including some test certs that are required here. Upstream has been made aware of the issue. So really this test cannot run at all, yet. If upstream doesn't fix this test soon then maybe we can disable it for now.
Fixed in 0.18 (they're finally shipping the required certs for this test)
Did a quick test of 0.18 on the 32bit profile of my Talos. test-eapol passes indeed now, thanks! But test-sae fails. Should I open a seperate bug? ================================ iwd 0.18: ./test-suite.log ================================ # TOTAL: 18 # PASS: 17 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-sae =================== test-sae: unit/test-sae.c:250: test_confirm_timeout: Assertion `auth_proto_rx_authenticate(ap, (uint8_t *)frame, len) == 0' failed. FAIL unit/test-sae (exit status: 134)
Did run the tests again with iwd-9999. All pass now on ppc.
