riot-os / release-specs Goto Github PK
View Code? Open in Web Editor NEWSpecification for RIOT releases and corresponding test configurations
Specification for RIOT releases and corresponding test configurations
This issue lists the status of all tests for the Release Candidate 2 of the 2015.12 release.
Specs tested:
samr21-xpro
node:Initializing ADT7310 sensor... [Failed]
*ifconfig
doesn't show up the ethernet device since its not attachedInitializing HIH6130 sensor at I2C_0, address 0x27... [OK] Communication error: -1
, since no HIH6130 sensor is attachedInitializing ISL29125 sensor at I2C_0... [Failed]
Initializing LIS3DH sensor... [Failed]
Initializing LSM303DLHC sensor at I2C_0... [Failed]
Initializing MPL3115A2 sensor at I2C_0... [Failed]
it
fails with all read registers are 0
Testing sensor communication...[Failed]
, since no SI7021 temperature and humidity sensor is attachedInitializing TCS37727 sensor at I2C_0... [Failed]
, since its not attached265 us
difference to expected 1s
min
running drift/jitter
max: ~170 uslist made manually by executing:
ls -1a | sed -e 's/^/- [ ] /'
in RIOT/tests
and removing unittests
et al. from the list
This issue lists the status of all tests for the Release Candidate 2 of the 2016.10
Specs tested:
This issue lists the status of all tests for the Release Candidate 1 of the 2017.10 release.
Specs tested:
iotlab-m3
node:ENC_RST
GPIO pin must be set to a different pin for this test, e.g. 0,7, since it conflicts with the onboard transceiver sleep pin)periph_pwm
is not available on this board)make test
fails RIOT-OS/RIOT#6533, calling ps
in the shell spams a wall of garbage in the shell)list made manually by executing:
ls -1a | sed -e 's/^/- [ ] /'
in RIOT/tests
and removing unittests
et al. from the list
This issue lists the status of all tests for the Release Candidate 1 of the 2018.01 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 4 of the 2015.09 release.
Specs tested:
1000 packets transmitted, 1000 received, 0% packet loss, time 10.06155388 s
(and pktbuf is empty)1000 packets transmitted, 1000 received, 0% packet loss, time 100.06267042 s
3600 packets transmitted, 3600 received, 0% packet loss, time 3600.06266335 s
1000 packets transmitted, 1000 received, 0% packet loss, time 18.06298406 s
1000 packets transmitted, 1000 received, 0% packet loss, time 119.06712665 s
(and pktbuf is empty)1000 packets transmitted, 998 received, 1% packet loss, time 243.06217368 s
10000 packets transmitted, 9996 received, 1% packet loss, time 1222.06596852 s
100 packets transmitted, 100 received, 0% packet loss, time 1.0619766 s
100 packets transmitted, 99 received, 1% packet loss, time 16.06761171 s
10 packets transmitted, 10 received, 0% packet loss, time 0.0693490 s
Packets received: 999
(forgot to add od
, so no pktbuf
check possible, but should be alright)window: [87, 104, 118, 144]
Setting route dead:beef::90 via fe80::3432:4833:46d8:8a16 for m3-87 ...success
Setting route :: via fe80::3432:4833:46d4:8822 for m3-104 ... success
Setting route dead:beef::90 via fe80::3432:4833:46df:8922 for m3-104 ...success
Setting route :: via fe80::3432:4833:46d8:8a16 for m3-118 ... success
Setting route dead:beef::90 via fe80::3432:4833:46da:9672 for m3-118 ...success
Setting route :: via fe80::3432:4833:46df:8922 for m3-144 ... success
Pinging (dead:beef::90) for node m3-87 ... success with 0% packet loss
Successfully pinged with 3 hops
SUCCESS
window: [162, 163, 165, 176]
Setting route dead:beef::b0 via fe80::3432:4833:46de:8922 for m3-162 ...success
Setting route :: via fe80::3432:4833:46d5:8a36 for m3-163 ... success
Setting route dead:beef::b0 via fe80::3432:4833:46d8:8726 for m3-163 ...success
Setting route :: via fe80::3432:4833:46de:8922 for m3-165 ... success
Setting route dead:beef::b0 via fe80::3432:4833:46d4:8d26 for m3-165 ...success
Setting route :: via fe80::3432:4833:46d8:8726 for m3-176 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Send UDP to dead:beef::b0 from node m3-162 ... success
Sent successfully with packet loss of 0.0%
Successfully communicated with UDP over 3 hops
SUCCESS
1000000 packets transmitted, 1000000 received, 0% packet loss, time 33466ms
100000 packets transmitted, 100000 received, 0% packet loss, time 3684ms
100000 packets transmitted, 100000 received, 0% packet loss, time 3.06685815 s
100000 packets transmitted, 99648 received, 0% packet loss, time 1010348ms
100000 packets transmitted, 93395 received, 7% packet loss, time 21539.06641653 s
iotlab-m3
node:INFO # checking 10000 elements took 2145ms
INFO #
INFO # 267 elements probably in the filter.
INFO # 9733 elements not in the filter.
INFO # false positive rate.
INFO #
INFO # All done!
This list is based on previous #23 with different test marked for this release. I also added the new ones which are systematically performed.
This issue lists the status of all tests for the Release Candidate 2 of the 2017.07 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 1 of the 2015.09 release.
Specs tested:
1000 packets transmitted, 999 received, 1% packet loss, time 23.06321836 s
1000 packets transmitted, 1000 received, 0% packet loss, time 113.06589983 s
1000 packets transmitted, 992 received, 1% packet loss, time 280.06967510 s
100 packets transmitted, 100 received, 0% packet loss, time 1.0618546 s
100 packets transmitted, 100 received, 0% packet loss, time 15.06920354 s
10 packets transmitted, 10 received, 0% packet loss, time 0.0692178 s
100 packets transmitted, 100 received, 0% packet loss, time 6.06885310 s
Part of the script to create the list:
find "$BASEDIR" -maxdepth 2 -mindepth 2 -type f \ \( -name 'main.c' -or -name 'main.cpp' \) \ -exec grep -Eq '@ingroup[[:blank:]]+\<test' {} \; \ -print | sed 's#^\(.*\)/[^/]*$#\1#' | sort > "$LIST"
Create the markdown:
sed -e 's#^.*/\([^/]*\)$#- [ ] \1#' "$LIST"
Somehow ~600ms after boot, xtimer overflows the first time. Somehow, that causes trouble.
See #12.
Let's collect the test results for 02-tests here, task by task.
Status of all tests for the Release Candidate 3 of the 2015.12 release.
Please check off all tests that performed successfully. Inline any errors/warnings you encounter in this list.
The names I assigned are tentative. Feel free to re-assign or execute tests that are not marked with your name.
texts/libfixmath
some errors, see dump at #12 (comment)tests\xtimer_hang
results in an access violation on make term
Release 2016.04 - RC2This issue lists the status of all tests for the Release Candidate 2 of the 2016.04 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 2 of the 2017.04 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 3 of the 2016.10
Specs tested:
Why does Task 7 ask for a success rate of <10% for UDP packets but a success rate of <20% for ICMPv6 packets? What -- in the author's mind -- made UDP (uses 8 byte header, has checksum, might be header compressed) more successful at delivering packets than ICMPv6 (uses 8 byte header, has checksum, is not header compressed). Just the fact that one is compressed and the other not?
Status of all tests for the Release Candidate 4 of the 2015.12 release.
Please check off all tests that performed successfully. Inline any errors/warnings you encounter in this list.
The names I assigned are tentative. Feel free to re-assign or execute tests that are not marked with your name.
samr21-xpro
node:list made manually by executing:
ls -1a | sed -e 's/^/- [ ] /'
in RIOT/tests
and removing unittests
et al. from the list
ifconfig
(no interfaces as expected))This issue lists the status of all tests for the Release Candidate 2 of the 2015.09 release.
Specs tested:
1000 packets transmitted, 1000 received, 0% packet loss, time 10.06171217 s
1000 packets transmitted, 1000 received, 0% packet loss, time 100.06128933 s
3600 packets transmitted, 3600 received, 0% packet loss, time 3599.06917114 s
1000 packets transmitted, 1000 received, 0% packet loss, time 18.06335692 s
1000 packets transmitted, 999 received, 1% packet loss, time 109.06740717 s
1000 packets transmitted, 993 received, 1% packet loss, time 276.06342833 s
10000 packets transmitted, 9998 received, 1% packet loss, time 1313.06892156 s
100 packets transmitted, 100 received, 0% packet loss, time 1.0614627 s
100 packets transmitted, 100 received, 0% packet loss, time 16.068110 s
10 packets transmitted, 10 received, 0% packet loss, time 0.0692516 s
This issue lists the status of all tests for the Release Candidate 2 of the 2017.01 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 1 of the 2015.12 release.
Specs tested:
fib_sr
tests still failing (see RIOT-OS/RIOT#4513)/dev/random
dry./usr/local/src/RIOT/tests/periph_rtc/bin/native/periph_rtc.elf: rtc_set_time: not implemented
. No Alarms.Testing... (25%) make: *** [term] Segmentation fault
147 diff=3007\ too large difference.\ Test Failed
Sometimes fails sometimes not.This issue lists the status of all tests for the Release Candidate 1 of the 2017.01 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 2 of the 2017.10 release.
NOTE
Please report all findings to this table
NOTE
Specs tested:
This issue lists the status of all tests for the Release Candidate 3 of the 2015.09 release.
Specs tested:
This issue lists the status of all tests before the Release Candidate 1 of the 2015.12 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 4 of the 2016.10
Specs tested:
native
and check their output:samr21-xpro
when BOARD
is not set, build with BOARD=native make
for the expected build fail-
on the screeniotlab-m3
when BOARD
is not set, build with BOARD=native make
malloc
tested yet since I don't want to wait for filling my whole RAM with 1024 byte chunksf: rtc_set_alarm: not implemented
UART used for STDIO (the shell): UART_DEV(-1)
No SAUL devices present
list made manually performing:
ls -1a | sed -e 's/^/- [ ] /'
in RIOT/tests
This issue lists the status of all tests for the Release Candidate 3 of the 2016.04 release.
Specs tested:
iotlab-m3
node:ping6
)dht_read(dev, &temp, &hum)
, since no DHT 11/22 temperature and humidity sensor is attachedInitializing HDC1000 sensor at I2C_0... [Failed]
Initializing MMA8652 accelerometer at I2C_0... [Failed]
Verifying contents... [Failed]
-
on the screendrift/jitter
is about +-35 us
(these high values occured ~ 4 times a min
)list made manually by executing:
ls -1a | sed -e 's/^/- [ ] /'
in RIOT/tests
and removing unittests
et al. from the list
This issue lists the status of all tests for the Release Candidate 1 of the 2017.07 release.
Specs tested:
samr21-xpro
node:This list is based on previous #24 with different test marked for this release. I also added the new ones which are systematically performed.
This issue lists the status of all tests for the Release Candidate 5 of the 2015.09 release. Only native related specs and those which were not tested in #7 are required here.
Specs tested:
1000 packets transmitted, 1000 received, 0% packet loss, time 10.06728395 s
1000 packets transmitted, 1000 received, 0% packet loss, time 100.06765821 s
3600 packets transmitted, 3600 received, 0% packet loss, time 3600.06916673 s
100 packets transmitted, 100 received, 0% packet loss, time 1.0692095 s
10 packets transmitted, 10 received, 0% packet loss, time 0.06102241 s
1000000 packets transmitted, 1000000 received, 0% packet loss, time 202.06653731 s
100000 packets transmitted, 83292 received, 16% packet loss, time 1231630ms
100000 packets transmitted, 99770 received, 0% packet loss, time 5055033ms
iotlab-m3
node:INFO # checking 10000 elements took 2145ms
INFO #
INFO # 267 elements probably in the filter.
INFO # 9733 elements not in the filter.
INFO # false positive rate.
INFO #
INFO # All done!
periph_dac
module is not provided for iotlab-m3This list is based on previous #23 with different test marked for this release. I also added the new ones which are systematically performed.
When testing for the last release I wondered why UDP over 6LoWPAN has less error margin (<5%) than ICMPv6 over 6LoWPAN (<10%). Especially since Task 6 asks for way harder to deliver 1kB, while some of Task 5's specs only ask for 0B. Is there a specific reason for these 5%?
The other questionable thing more from a timing constraint is: Why does the delay need to be 1s? For testing it is really a long amount of time to send 1000 packets (~17min), while the tests would be as significant if the interval between them would be 50ms or 100ms.
Part of the script to create the list:
find "$BASEDIR" -maxdepth 2 -mindepth 2 -type f \ \( -name 'main.c' -or -name 'main.cpp' \) \ -exec grep -Eq '@ingroup[[:blank:]]+\<test' {} \; \ -print | sed 's#^\(.*\)/[^/]*$#\1#' | sort > "$LIST"
Create the markdown:
sed -e 's#^.*/\([^/]*\)$#- [ ] \1#' "$LIST"
All performed tests have a checkmark and are either success, failed (with short comment) or have an unclear result (at least for me).
This issue lists the status of all tests for the Release Candidate 1 of the 2016.07 release.
Specs tested:
Building for ARM-Cortex platforms currently fails for me with:
arm-none-eabi-g++ \
-DRIOT_FILE_RELATIVE=\"tests/cpp11_condition_variable/main.cpp\" \
-DRIOT_FILE_NOPATH=\"main.cpp\" \
-Werror -mcpu=cortex-m3 -mlittle-endian -mthumb -mfloat-abi=soft -mno-thumb-interwork -ffunction-sections -fdata-sections -fno-builtin -fshort-enums -ggdb -g3 -Os -fno-delete-null-pointer-checks -Werror=strict-prototypes -Werror=old-style-definition -fno-common -Wall -include '/home/oleg/git/RIOT/tests/cpp11_condition_variable/bin/cc2538dk/riotbuild/riotbuild.h' -std=c++11 -isystem /usr/arm-none-eabi/include/nano -isystem /usr/arm-none-eabi/include -I/home/oleg/git/RIOT/core/include -I/home/oleg/git/RIOT/drivers/include -I/home/oleg/git/RIOT/sys/include -I/home/oleg/git/RIOT/cpu/cc2538/include -I/home/oleg/git/RIOT/boards/cc2538dk/include -I/home/oleg/git/RIOT/cpu/cortexm_common/include -I/home/oleg/git/RIOT/sys/libc/include -I/home/oleg/git/RIOT/sys/cpp11-compat/include -MD -MP -c -o /home/oleg/git/RIOT/tests/cpp11_condition_variable/bin/cc2538dk/cpp11_condition_variable/main.o /home/oleg/git/RIOT/tests/cpp11_condition_variable/main.cpp
In file included from /usr/arm-none-eabi/include/c++/6.2.0/ext/string_conversions.h:41:0,
from /usr/arm-none-eabi/include/c++/6.2.0/bits/basic_string.h:5402,
from /usr/arm-none-eabi/include/c++/6.2.0/string:52,
from /home/oleg/git/RIOT/tests/cpp11_condition_variable/main.cpp:21:
/usr/arm-none-eabi/include/c++/6.2.0/cstdlib:75:25: fatal error: stdlib.h: No such file or directory
#include_next <stdlib.h>
^
However:
`# ls -lah /usr/arm-none-eabi/include/c++/6.2.0/stdlib.h
-rw-r--r-- 1 root root 2.2K Aug 31 19:52 /usr/arm-none-eabi/include/c++/6.2.0/stdlib.h
This issue lists the status of all tests for the Release Candidate 1 of the 2016.10 release.
Specs tested:
Router and host configurations differ in IPv6 NDP with regards to their behavior. In my opinion this should also be reflected in the release specs. Opinions on that?
This issue lists the status of all tests for the Release Candidate 1 of the 2017.04 release.
Specs tested:
This issue lists the status of all tests for the Release Candidate 1 of the 2016.04 release.
Specs tested:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.