-
Notifications
You must be signed in to change notification settings - Fork 2.1k
test/pkg/relic: increase stacksize for paillier encryption #21306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
c76ba2a
to
a8232be
Compare
I tested Paillier encryption with 512-bit key using |
Hum, could you paste the stacksizes reported at the end of the test here? I'd guess this could have to do with a different
I can't test on |
I tested Paillier with 512 bit key using my own program. When I investigated this issue I remember that I manually set stack size
|
Sure, I guess that's expected. But to avoid the giant stacksize requirement which would effectively prevent HIL tests on the |
I have just checked that for example Yes, reducing the stack size, relic precision and Paillier key size is a good idea. |
a8232be
to
285dc27
Compare
Thanks everyone! |
Contribution description
The Paillier encryption test from #21301 seems to require a much larger stack, leading the last nightly to fail on the HIL test: https://ci.riot-os.org/details/c88f567b8ff94d0484073f3151c18529/tests
Instead of only increasing the stack (tested to require
25*THREAD_STACKSIZE_DEFAULT
on aBOARD=nrf52840dk
), leading to insufficient memory onBOARD=samr21-xpro
, I've also halfed the relic big number precision to 512 bits, allowing for paillier encryption up to 256 bits as it seems.Testing procedure
With this reduced precision and the increased stacksize, we get
and
I'll run a no-fast-fail build to get all boards with insufficient memory issues.
Issues/PRs references
Fixup after #21301, tagging @krzysztof-cabaj as its author.