-
Notifications
You must be signed in to change notification settings - Fork 21
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
spec11: harden testing #255
Conversation
There seems to be (appearently unrelated) issue where task 3 can't complete since the lorawan_tx fails. TTN does not show any packets for that, @jia200x is currently trying to figure out what went wrong. |
bb3d89b
to
96b0f19
Compare
It appears, the only reason https://github.com/RIOT-OS/RIOT/runs/7673103443?check_suite_focus=true fails now is because the experiment is suddenly stopped while the device tries to send. @aabadie @fjmolinas do you know if that is a known problem? |
From the discussion in #258 (comment), I was thinking: maybe it makes sense to additionally add a blacklist feature for nodes. I.e. if the test fails, add the capability to mark the failing node as defect, and rerun with another. I will investigate this. |
389f555
to
2c3c812
Compare
2c3c812
to
ba6bd20
Compare
When removing this, the ABP tests succeed more reliable
ba6bd20
to
c0774b6
Compare
Squashed. |
This introduces several changes to the LoRaWAN tests, in the hopes to not make them fail that regular anymore:
tx_delay
)Add some grace time to the waiting between sending from the node and receiving at the TTN clientIncrease expect timeout onlorawan_tx
for task03ul_cnt
setting. When set, TX for some reason never succeeds.