aboutsummaryrefslogtreecommitdiffstats
path: root/lib/common_test/src/ct_hooks_lock.erl
diff options
context:
space:
mode:
authorAndreas Schultz <[email protected]>2017-05-03 16:25:10 +0200
committerAndreas Schultz <[email protected]>2017-05-03 16:25:10 +0200
commit16c1a5dab6435f595c2a8c252288f37039ceab12 (patch)
treed3606001fe780644ccfc8369268b0f731f85f9e9 /lib/common_test/src/ct_hooks_lock.erl
parent44ae0703c559f78c4d2681e4e2620bf47fe7afd6 (diff)
downloadotp-16c1a5dab6435f595c2a8c252288f37039ceab12.tar.gz
otp-16c1a5dab6435f595c2a8c252288f37039ceab12.tar.bz2
otp-16c1a5dab6435f595c2a8c252288f37039ceab12.zip
crypto: use lazy evaluation for test cases read from CAVP files
It turns out that the excessive memory usage is cause by the test framework printing all the test vectors into the log output. A similar proplem was already diagnosed for long_msg/0. The root cause was not mentioned in the SUITE, but the same fix applies to the CAPV test vector data. Switch all CAPV data to lazy evaluation and have the test itself read the data.
Diffstat (limited to 'lib/common_test/src/ct_hooks_lock.erl')
0 files changed, 0 insertions, 0 deletions