summaryrefslogtreecommitdiff
path: root/Cryptlib/OpenSSL/crypto/cryptlib.c
diff options
context:
space:
mode:
authorPeter Jones <pjones@redhat.com>2025-01-18 12:33:09 -0500
committerPeter Jones <pjones@redhat.com>2025-02-24 15:24:24 -0500
commite4857b4150b0a982d587ea9ccbc73137e8887fd8 (patch)
treeefb378f4fe45ae9db41a0fe459111fe4cb2900a4 /Cryptlib/OpenSSL/crypto/cryptlib.c
parent887c0edab93c52e2558047897847166b73dc8c3a (diff)
downloadefi-boot-shim-e4857b4150b0a982d587ea9ccbc73137e8887fd8.tar.gz
efi-boot-shim-e4857b4150b0a982d587ea9ccbc73137e8887fd8.zip
Make test-mok-error failures *slightly* more clear.
Currently when you've added a variable and not correctly changed the test cases to match, you get a message like: ./test-mok-mirror test-mok-mirror: setting variable sort policy to MOCK_SORT_DESCENDING test-mok-mirror: setting delete policy to MOCK_VAR_DELETE_ATTR_ALLOW_ZERO running test_mok_mirror_with_enough_space test_mok_mirror_with_enough_space: passed running test_mok_mirror_setvar_out_of_resources check_config_table:232:mok.name[0] 72 != test.name[0] 0 check_config_table:232:Assertion `mok_entry->name[0] == mock_entry->name[0]' failed. This adds another two lines: test-mok-mirror: Failed on entry 4 mok.name:"HSIStatus" mock.name:"" test-mok-mirror: Entry is missing in expected variable list. Or: test-mok-mirror: Failed on entry 4 mok.name:"" mock.name:"HSIStatus" test-mok-mirror: Entry is missing in found variable list. Which will usually tell you which variable you forgot to add that's present in test data, or what's missing in the test data and present in the expected data. Signed-off-by: Peter Jones <pjones@redhat.com>
Diffstat (limited to 'Cryptlib/OpenSSL/crypto/cryptlib.c')
0 files changed, 0 insertions, 0 deletions