Hi, On 01-02-2020 13:43, Илья Шипицин wrote: > https://travis-ci.org/chipitsine/openvpn/jobs/644745481?utm_medium=notification&utm_source=github_status > > it indicates "ERROR" when running tests, however tests are ok after all. > > [ RUN ] tls_crypt_v2_wrap_too_long_metadata > > ERROR: could not crypt: insufficient space in dst > > [ OK ] tls_crypt_v2_wrap_too_long_metadata > > [ RUN ] tls_crypt_v2_wrap_unwrap_wrong_key > > [ OK ] tls_crypt_v2_wrap_unwrap_wrong_key > > [ RUN ] tls_crypt_v2_wrap_unwrap_dst_too_small > > [ OK ] tls_crypt_v2_wrap_unwrap_dst_too_small > > [ RUN ] test_tls_crypt_v2_write_server_key_file > > [ OK ] test_tls_crypt_v2_write_server_key_file > > [ RUN ] test_tls_crypt_v2_write_client_key_file > > [ OK ] test_tls_crypt_v2_write_client_key_file > > [==========] 14 test(s) run. > > [ PASSED ] 14 test(s). > > PASS: tls_crypt_testdriver
This is expected behaviour. And unrelated to arm64. Just check the amd64 build, exact same message. We test the "too much input data" case here, which prints an error. Looks odd, I admit. But printing warnings/errors even in tests helps speed up diagnosis. -Steffan _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
