Currently python unit test failures are ignored.
Fix this.
Currently python unit test failures are ignored.
Fix this.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For detailed information about the code coverage, see the test coverage report.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | theStack, BrandonOdiwuor |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Can be tested with something like:
0diff --git a/test/functional/test_framework/crypto/bip324_cipher.py b/test/functional/test_framework/crypto/bip324_cipher.py
1index 56190647f2..56211e231d 100644
2--- a/test/functional/test_framework/crypto/bip324_cipher.py
3+++ b/test/functional/test_framework/crypto/bip324_cipher.py
4@@ -89,7 +89,7 @@ class FSChaCha20Poly1305:
5 # Test vectors from RFC8439 consisting of plaintext, aad, 32 byte key, 12 byte nonce and ciphertext
6 AEAD_TESTS = [
7 # RFC 8439 Example from section 2.8.2
8- ["4c616469657320616e642047656e746c656d656e206f662074686520636c6173"
9+ ["5c616469657320616e642047656e746c656d656e206f662074686520636c6173"
10 "73206f66202739393a204966204920636f756c64206f6666657220796f75206f"
11 "6e6c79206f6e652074697020666f7220746865206675747572652c2073756e73"
12 "637265656e20776f756c642062652069742e",
And then calling ./test/functional/test_runner.py ; echo $?
Fun fact: This problem would not exist in a type-safe language.
It’s time to start rewriting code in such a language.