First the comment does not fit these two boards and
second they would work compiler wise but just do not
have an SPI to support the radio. Hence, won't be
used due to missing features.
If the destination address or an address within the source route is
multicast within a RPL source routing header, a receiving node is
supposed to just discard the packets, but not to send an ICMPv6 error
message, as the test assumes at the moment.
Source: https://tools.ietf.org/html/rfc6554#section-4.2
Two Functions cmd_test_xtimer_mutex_lock_timeout_low_prio_thread and thread_low_prio_test are added.
This testfunction will test xtimer_mutex_lock_timeout with two threads (main thread and lower prio than main thread).
The main thread creates another thread and sleeps. While the main thread sleeps the other thread takes the mutex
and wakes the main thread up.
Then the main thread calls xtimer_mutex_lock_timeout and the second thread unlocks the mutex and
the main thread gets it and waits for the created thread to end.
Has test messages showing the thread count. To make sure the created thread ends.
(test messages may be removed in the future)
Adds a test case for when the following conditions cause a crash:
- a subsequent fragment is received before the first
- the reassembly buffer is currently filled up when another fragment of
a different datagram arrives and thus needs to be cached out to make
room for the new reassembly
Printing the 'Received ...' string takes a short while and it is possible
that data is received while the string is printed. It seems however that
NimBLE does not like to be without a mbuf ready for taking data while
receiving something, as this seems to lead to a memory leak somehow. Now
changing the order of actions inside the _on_data() function fixes this.
While looking at tests/gnrc_ipv6_ext_frag again while writing
RIOT-OS/Release-Specs#137, I noticed that several of tests that I
definitely wrote myself from scretch are attributed wrong (and
sometimes even documented wrong). I guess this was caused by just
copy-pasting the files...
The test application now correctly prints float value, with a 3 digits precision. The python test script now verifies the run time value printed for each test is following the x.xxx pattern.
