tests/tweetnacl: Move from unittests to regular test#10184
tests/tweetnacl: Move from unittests to regular test#10184cladmi merged 1 commit intoRIOT-OS:masterfrom
Conversation
|
This one is not as bad as the others, "only" 33 seconds: |
4ad9705 to
2dd3dba
Compare
|
rebased |
|
@kaspar030 Ready to squash? Does your ACK still hold with the recent changes? |
|
I get a 'context before hardfault' error on My toolchain: |
|
On the |
|
Ah, never noticed the hard fault because the |
tests/pkg_tweetnacl/Makefile
Outdated
|
|
||
| TEST_ON_CI_WHITELIST += native | ||
|
|
||
| CFLAGS += -DTHREAD_STACKSIZE_MAIN=\(4*THREAD_STACKSIZE_DEFAULT\) |
There was a problem hiding this comment.
Using the stack size value used in unittests works without crash:
| CFLAGS += -DTHREAD_STACKSIZE_MAIN=\(4*THREAD_STACKSIZE_DEFAULT\) | |
| CFLAGS += -DTHREAD_STACKSIZE_MAIN=\(4*THREAD_STACKSIZE_DEFAULT+THREAD_EXTRA_STACKSIZE_PRINTF\) |
There was a problem hiding this comment.
I've incremented the "4" to "5".
There was a problem hiding this comment.
Agreed if you put the comment in the commit too as mentioned in #10185 (comment)
cladmi
left a comment
There was a problem hiding this comment.
Currently tests are broken.
|
@cladmi Thanks for testing, I've increased the stack size a bit. With that the test succeeds on the samr21-xpro |
cladmi
left a comment
There was a problem hiding this comment.
ACK the tests now works on iotlab-m3 and samr21-xpro please squash.
When doing it please include something like this in the commit message to explain the stack size: #10185 (comment)
9a0fffc to
7bba650
Compare
|
squashed. Included the same information in the PR as with #10185 |
|
For info on stack
Currently it crashes on There is also one board that should be removed because of not enough memory: |
|
I agree with the commit message. |
|
For So better blacklist it anyway. |
But it doesn't fail 😆 |
tests/pkg_tweetnacl/Makefile
Outdated
|
|
||
| BOARD_INSUFFICIENT_MEMORY := arduino-duemilanove \ | ||
| arduino-uno \ | ||
| arduino-mega2560 \ |
There was a problem hiding this comment.
Update not pushed or github lagging ?
|
@cladmi I've blacklisted both the arduino-mega2560 and the mega-xplained. That last one is probably as slow as as the first one. |
|
Please rebase and squash with the commit message saying we now blacklisted the boards with the reason. |
|
No need for "run tests" as |
b416de8 to
ed84bc7
Compare
|
Squashed and rebased. Mentioned the arduino boards in the commit message |
| arduino-mega2560 \ | ||
| mega-xplained \ | ||
| nucleo-f031k6 \ | ||
| # |
There was a problem hiding this comment.
Just missing the nucleo-f042k6 here to make murdock happy. You can inline squash it to test it directly so it is ready to merge after.
There was a problem hiding this comment.
Just missing the
nucleo-f042k6here to makemurdockhappy. You can inline squash it to test it directly so it is ready to merge after.
Fixed -_-
86b82fc to
78cbfc8
Compare
|
Just waiting for murdock and it can be merged! |
|
Thank you for following with the fixes and updates. |
|
Do you want me to squash that last commit? |
|
As you wish. |
Stack size is changed from 4 times the default + printf to 5 times the default stack size. Only on the lpc2387 this reduces the resulting stack space. the test is not rerun for the lpc2387 and is untested. Tests are disable for the Arduino. While they "might" work, it takes around 8 minutes to complete the tests.
e0d3225 to
137e482
Compare
|
Unreliable native test again… I restart murdock. |
|
Thank you for taking care of the migration ! :) |
Contribution description
Similar to #10183.
Testing procedure
I suspect that the test works on AVR and msp430, but I'm not sure. Testing this is preferred in case those need to be blacklisted
Insufficient memory list is manually generated based on the
tests/pkg_libcoseblacklist and memory list.Issues/PRs references
Part of #10187