Closed jia200x closed 6 years ago
I take care of running 01-ci -> Task #01 in docker with:
@kb2ma is working on running coap tests https://github.com/RIOT-OS/Release-Specs/pull/77 :)
I still have the arch image I used for testing https://github.com/RIOT-OS/RIOT/pull/9942 on stronger machine, so I will run 1.1 with that as well during the night.
updated tasks with script
I still have the arch image I used for testing RIOT-OS/RIOT#9942 on stronger machine, so I will run 1.1 with that as well during the night.
Sadly, I've got massive problems using that VM... I'll try tomorrow again, but for now I'm leaving.
5 tests failed on native
. Some of them false positives. Check the logs here
The cayenne-lpp and lora-serialization issues are similar to what we saw with https://github.com/RIOT-OS/RIOT/pull/9681, I think.
For the my9221
test some proper config is needed from your side.
The driver_at
test seems to be the only legitimate error, as it marks a casting of a function pointer to a completely different type.
The cayenne-lpp and lora-serialization issues are similar to what we saw with RIOT-OS/RIOT#9681, I think.
Yes, it's the same.
The driver_at test seems to be the only legitimate error, as it marks a casting of a function pointer to a completely different type.
Agreed :)
on samr21-xpro all tests pass but driver_my9221
and pkg_fatfs_vfs
. But for the same reasons as described in this comment
What I notice too with lora-serialization
is that it overrides the test
target.
make RIOT_CI_BUILD=1 CC_NOCOLOR=1 --no-print-directory -C /home/jialamos/Development/RIOT/tests/pkg_lora-serialization test
Makefile:9: warning: overriding recipe for target 'test'
For the
my9221
test some proper config is needed from your side.
That is something that should then be selected using features I think. But it is a global change and not a bug fixup. It goes in my dependencies definitions huge todo list.
The driver_at already has a pull request for it https://github.com/RIOT-OS/RIOT/pull/9740
btw, there are some weird results in the trickle
test in some boards, and I'm not able to reproduce them.
E.g samr21-xpro:
make RIOT_CI_BUILD=1 CC_NOCOLOR=1 --no-print-directory -C /home/kevinweiss/WorkingDirectory/RIOT/tests/trickle test
ssh -oProxyCommand="ssh weiss@riot-ci.inet.haw-hamburg.de -W %h:%p" -t pi@10.28.48.11 'socat - open:/dev/ttyACM0,b115200,echo=0,raw'
main(): This is RIOT! (Version: buildtest)
[START]
now = 44987, prev_now = 3935, diff = 41052
now = 138904, prev_now = 44987, diff = 93917
now = 380000, prev_now = 138904, diff = 241096
now = 830277, prev_now = 380000, diff = 450277
now = 1648560, prev_now = 830277, diff = 818283
[TRICKLE_RESET]
now = 1666973, prev_now = 1648560, diff = 18413
now = 1694341, prev_now = 1666973, diff = 27368
now = 1772710, prev_now = 1694341, diff = 78369
now = 1845080, prev_now = 1772710, diff = 72370
[FAILURE]
Timeout in expect script at "child.expect(u"now = \d+, prev_now = \d+, diff = \d+")" (tests/trickle/tests/01-run.py:22)
/home/kevinweiss/WorkingDirectory/RIOT/tests/trickle/../../Makefile.include:557: recipe for target 'test' failed
make: *** [test] Error 1
With toolchain
Operating System Environment
-----------------------------
Operating System: "Ubuntu" "16.04.5 LTS (Xenial Xerus)"
Kernel: Linux 4.15.0-38-generic x86_64 x86_64
Installed compiler toolchains
-----------------------------
native gcc: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
arm-none-eabi-gcc: arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
avr-gcc: avr-gcc (GCC) 4.9.2
mips-mti-elf-gcc: missing
msp430-gcc: missing
riscv-none-embed-gcc: missing
clang: clang version 5.0.0-3~16.04.1 (tags/RELEASE_500/final)
Installed compiler libs
-----------------------
arm-none-eabi-newlib: "2.5.0"
mips-mti-elf-newlib: missing
riscv-none-embed-newlib: missing
avr-libc: "1.8.0svn" ("20111229")
Installed development tools
---------------------------
cmake: cmake version 3.5.1
cppcheck: missing
doxygen: missing
flake8: 3.5.0 (mccabe: 0.6.1, pycodestyle: 2.3.1, pyflakes: 1.6.0) CPython 3.5.2 on Linux
git: git version 2.7.4
openocd: Open On-Chip Debugger 0.10.0+dev-00399-g09076d1 (2018-04-12-17:12)
python: Python 2.7.12
python2: Python 2.7.12
python3: Python 3.5.2
coccinelle: missing
I managed to compile everything with docker xenial
using gcc
except waspmote-pro/tests_gnrc_ipv6_nib
that fails with
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: address 0x80210f of /data/riotbuild/riotproject/tests/gnrc_ipv6_nib/bin/waspmote-pro/tests_gnrc_ipv6_nib.elf section `.bss' is not within region `data'
/usr/lib/gcc/avr/4.9.2/../../../avr/bin/ld: address 0x80210f of /data/riotbuild/riotproject/tests/gnrc_ipv6_nib/bin/waspmote-pro/tests_gnrc_ipv6_nib.elf section `.bss' is not within region `data'
It is solved when using https://github.com/RIOT-OS/RIOT/pull/9646 so no need to worry about it.
archlinux% python task01.py ~/Development/RIOT
Building application "tests_gnrc_udp" for "native" with MCU "native".
"make" -C /home/jialamos/Development/RIOT/boards/native
"make" -C /home/jialamos/Development/RIOT/boards/native/drivers
"make" -C /home/jialamos/Development/RIOT/core
"make" -C /home/jialamos/Development/RIOT/cpu/native
"make" -C /home/jialamos/Development/RIOT/cpu/native/netdev_tap
"make" -C /home/jialamos/Development/RIOT/cpu/native/periph
"make" -C /home/jialamos/Development/RIOT/cpu/native/vfs
"make" -C /home/jialamos/Development/RIOT/drivers
"make" -C /home/jialamos/Development/RIOT/drivers/netdev_eth
"make" -C /home/jialamos/Development/RIOT/drivers/periph_common
"make" -C /home/jialamos/Development/RIOT/sys
"make" -C /home/jialamos/Development/RIOT/sys/auto_init
"make" -C /home/jialamos/Development/RIOT/sys/auto_init/netif
"make" -C /home/jialamos/Development/RIOT/sys/div
"make" -C /home/jialamos/Development/RIOT/sys/evtimer
"make" -C /home/jialamos/Development/RIOT/sys/fmt
"make" -C /home/jialamos/Development/RIOT/sys/iolist
"make" -C /home/jialamos/Development/RIOT/sys/luid
"make" -C /home/jialamos/Development/RIOT/sys/net/crosslayer/inet_csum
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netapi
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netif
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netif/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netreg
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/icmpv6
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/icmpv6/echo
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6/nib
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ndp
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pkt
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pktbuf
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pktbuf_static
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/routing/rpl
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/transport_layer/udp
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/icmpv6
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/ipv6/addr
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/ipv6/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/transport_layer/udp
"make" -C /home/jialamos/Development/RIOT/sys/od
"make" -C /home/jialamos/Development/RIOT/sys/ps
"make" -C /home/jialamos/Development/RIOT/sys/random
"make" -C /home/jialamos/Development/RIOT/sys/random/tinymt32
"make" -C /home/jialamos/Development/RIOT/sys/shell
"make" -C /home/jialamos/Development/RIOT/sys/shell/commands
"make" -C /home/jialamos/Development/RIOT/sys/trickle
"make" -C /home/jialamos/Development/RIOT/sys/xtimer
text data bss dec hex filename
219615 1169 102788 323572 4eff4 /home/jialamos/Development/RIOT/tests/gnrc_udp/bin/native/tests_gnrc_udp.elf
....................................................................................................OK
....................................................................................................OK
....................................................................................................OK
Summary of packet losses:
Run 1: 0
Run 2: 0
Run 3: 0
Average packet losses: 0.0
archlinux% python task02.py ~/Development/RIOT
.........................................................x..........................................OK
..........................................................x.........................................OK
.........................................................x..........................................OK
.........................................................x..........................................OK
..........................................................x.........................................OK
..........................................................x.........................................OK
....................................................................................................OK
.........................................................x..........................................OK
....................................................................................................OK
.........................................................x..........................................OK
{
"id": 139726,
"status": "Delete request registered"
}
Summary of packet losses:
Run 1: 1
Run 2: 1
Run 3: 1
Run 4: 1
Run 5: 1
Run 6: 1
Run 7: 0
Run 8: 1
Run 9: 0
Run 10: 1
Average packet losses: 0.8
Building application "tests_gnrc_udp" for "native" with MCU "native".
"make" -C /home/jialamos/Development/RIOT/boards/native
"make" -C /home/jialamos/Development/RIOT/boards/native/drivers
"make" -C /home/jialamos/Development/RIOT/core
"make" -C /home/jialamos/Development/RIOT/cpu/native
"make" -C /home/jialamos/Development/RIOT/cpu/native/netdev_tap
"make" -C /home/jialamos/Development/RIOT/cpu/native/periph
"make" -C /home/jialamos/Development/RIOT/cpu/native/vfs
"make" -C /home/jialamos/Development/RIOT/drivers
"make" -C /home/jialamos/Development/RIOT/drivers/netdev_eth
"make" -C /home/jialamos/Development/RIOT/drivers/periph_common
"make" -C /home/jialamos/Development/RIOT/sys
"make" -C /home/jialamos/Development/RIOT/sys/auto_init
"make" -C /home/jialamos/Development/RIOT/sys/auto_init/netif
"make" -C /home/jialamos/Development/RIOT/sys/div
"make" -C /home/jialamos/Development/RIOT/sys/evtimer
"make" -C /home/jialamos/Development/RIOT/sys/fmt
"make" -C /home/jialamos/Development/RIOT/sys/iolist
"make" -C /home/jialamos/Development/RIOT/sys/luid
"make" -C /home/jialamos/Development/RIOT/sys/net/crosslayer/inet_csum
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netapi
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netif
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netif/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/netreg
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/icmpv6
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/icmpv6/echo
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ipv6/nib
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/network_layer/ndp
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pkt
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pktbuf
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/pktbuf_static
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/routing/rpl
"make" -C /home/jialamos/Development/RIOT/sys/net/gnrc/transport_layer/udp
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/icmpv6
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/ipv6/addr
"make" -C /home/jialamos/Development/RIOT/sys/net/network_layer/ipv6/hdr
"make" -C /home/jialamos/Development/RIOT/sys/net/transport_layer/udp
"make" -C /home/jialamos/Development/RIOT/sys/od
"make" -C /home/jialamos/Development/RIOT/sys/ps
"make" -C /home/jialamos/Development/RIOT/sys/random
"make" -C /home/jialamos/Development/RIOT/sys/random/tinymt32
"make" -C /home/jialamos/Development/RIOT/sys/shell
"make" -C /home/jialamos/Development/RIOT/sys/shell/commands
"make" -C /home/jialamos/Development/RIOT/sys/trickle
"make" -C /home/jialamos/Development/RIOT/sys/xtimer
text data bss dec hex filename
219615 1169 102788 323572 4eff4 /home/jialamos/Development/RIOT/tests/gnrc_udp/bin/native/tests_gnrc_udp.elf
..........OK
..........OK
..........OK
Summary of packet losses:
Run 1: 0
Run 2: 0
Run 3: 0
Average packet losses: 0.0
archlinux% python task04.py ~/Development/RIOT
..........OK
..........OK
..........OK
..........OK
..........OK
..........OK
..........OK
..........OK
..........OK
..........OK
{
"id": 139724,
"status": "Delete request registered"
}
Summary of packet losses:
Run 1: 0
Run 2: 0
Run 3: 0
Run 4: 0
Run 5: 0
Run 6: 0
Run 7: 0
Run 8: 0
Run 9: 0
Run 10: 0
Average packet losses: 0.0
btw I used RIOT-OS/Release-Specs#79 for running the 05 tasks.
@RIOT-OS/maintainers can someone take care of the missing tasks? (e.g 03, 04, ...)
I noticed that currently it is not possible to build in docker from a release archive. I have a commit that fixes this in a bigger PR that was at first done for external applications. I will do a separate PR for this.
In bionic
and docker I have problems when running from a worktree
because git hash-object --stdin
complains in git-cache
. I will investigate more.
on samr21-xpro all tests pass but driver_my9221 and pkg_fatfs_vfs. But for the same reasons as described in this comment
pkg_fatfs_vfs
passes on samr21-xpro
.
@kb2ma I added the pointer to the CoAP tests PR so other people can find them. AFAIU, these 5 tasks where run in 2018.10-branch
, right?
driver_my9221
pass with fix in RIOT-OS/RIOT#10305 on samr21-xpro
.
So, besides the trickle
problem that I was not able to reproduce anymore, all tests are passing on samr21-xpro
.
AFAIU, these 5 tasks where run in 2018.10-branch, right?
Yes, that's correct.
I ran all tests on Iot-LAB (iotlab-m3
board). pkg_fatfs_vfs
and driver_my9221
failed because of configurations (as expected in this case).
The trickle
had the same issue as described here.
Also, there seems to be something wrong with I2C on IoT-LAB. drivers_ds1307
failed:
make RIOT_CI_BUILD=1 CC_NOCOLOR=1 --no-print-directory -C /home/jialamos/RIOT/tests/driver_ds1307 test
ssh -t alamos@grenoble.iot-lab.info 'socat - tcp:m3-100.grenoble.iot-lab.info:20000'
�main(): This is RIOT! (Version: buildtest)
DS1307 RTC test
.
tests.test_nvram (tests/driver_ds1307/main.c 89) exp "This is a test" was ""
�main(): This is RIOT! (Version: buildtest)
DS1307 RTC test
.
tests.test_nvram (tests/driver_ds1307/main.c 89) exp "This is a test" was ""
..
tests.test_halt (tests/driver_ds1307/main.c 117) exp 0 was -80
run 3 failures 2
Timeout in expect script at "r"error: unable to initialize RTC \[I2C initialization error\]"])" (tests/driver_ds1307/tests/01-run.py:15)
make: *** [/home/jialamos/RIOT/tests/driver_ds1307/../../Makefile.include:553: test] Error 1
Return value: 2
Compiled everything in the bionic
image and the failure (firmware too big) is the same as with the next xenial
image and the current one. It is just because of our docker integration
https://github.com/RIOT-OS/Release-Specs/issues/76#issuecomment-434270312
08-interop/T.09 works, but there's a problem in the implementation of the udp send
command in the emb6
test:
GNRC sending to emb6
1541163424.179446;m3-101;> udp send fe80::1711:6b10:65fc:5c22 80 abcdefgh
1541163424.181546;m3-101;Success: sent 8 byte(s) to [fe80::1711:6b10:65fc:5c22]:80
1541163424.182760;m3-100;Received from [c1d:20:a429:20:800:0:5000:0]:80:
1541163424.183683;m3-100;00000000 61 62 63 64 65 66 67 68
emb6 sending to GNRC
1541163434.433180;m3-100;udp send fe80::1711:6b10:65f6:5d02 80 abcdefgh
1541163434.435101;m3-100;Success: send 3 byte to [fe80::1711:6b10:65f6:5d02]:80)
1541163434.436805;m3-101;> PKTDUMP: data received:
1541163434.437796;m3-101;~~ SNIP 0 - size: 3 byte, type: NETTYPE_UNDEF (0)
1541163434.437988;m3-101;00000000 AB CD EF
emb6 is encoding the payload wrongly (see here). But it works (both with ICMP packets as well as UDP).
EDIT: In theory is not a bug because it's part of the documentation, but I opened RIOT-OS/RIOT#10316 anyway
See https://github.com/RIOT-OS/RIOT/issues/10316#issuecomment-435909204 on that. You may reopen if you disagree, but I don't think this needs to be "improved".
1541163424.182760;m3-100;Received from [c1d:20:a429:20:800:0:5000:0]:80:
The address outputed however seems to be a bug in the sock_udp_recv
implementation of emb6
. I also encountered that when testing task 8.10 I'll have a look.
Contiki test successful 👍🏽
For the record:
Contiki side:
Contiki-3.x-3148-geabb1ce3d
TI SmartRF06 + cc2538EM
CC2538: ID: 0xb965, rev.: PG2.0, Flash: 512 KiB, SRAM: 32 KiB, AES/SHA: 1, ECC/RSA: 1
System clock: 16000000 Hz
I/O clock: 16000000 Hz
Reset cause: External reset
Net: sicslowpan
MAC: CSMA
RDC: nullrdc
Rime configured with address 00:12:4b:00:04:22:9d:bd
Starting UDP echo server
Listen port: 3000, TTL=64
13 bytes from [fe80::7b65:334d:d1d6:fa52]:3000
It shows an UDP packet received from RIOT. Ping also works as expected:
> ping6 fe80::212:4b00:422:9dbd
2018-11-05 19:07:04,312 - INFO # ping6 fe80::212:4b00:422:9dbd
2018-11-05 19:07:04,324 - INFO # 12 bytes from fe80::212:4b00:422:9dbd: id=84 seq=1 hop limit=64 time = 7.647 ms
2018-11-05 19:07:05,346 - INFO # 12 bytes from fe80::212:4b00:422:9dbd: id=84 seq=2 hop limit=64 time = 7.963 ms
2018-11-05 19:07:06,366 - INFO # 12 bytes from fe80::212:4b00:422:9dbd: id=84 seq=3 hop limit=64 time = 7.332 ms
2018-11-05 19:07:06,371 - INFO # --- fe80::212:4b00:422:9dbd ping statistics ---
2018-11-05 19:07:06,377 - INFO # 3 packets transmitted, 3 received, 0% packet loss, time 2.0644872 s
2018-11-05 19:07:06,380 - INFO # rtt min/avg/max = 7.332/7.647/7.963 ms
And for UDP:
> udp send fe80::212:4b00:422:9dbd 3000 HELLO_CONTIKI
2018-11-05 19:07:36,253 - INFO # udp send fe80::212:4b00:422:9dbd 3000 HELLO_CONTIKI
2018-11-05 19:07:36,258 - INFO # Success: sent 13 byte(s) to [fe80::212:4b00:422:9dbd]:3000
Which reflects what was sent to the contiki node.
Side note: I tested it with the contiki version 3.1. For the next release we might want to move to contiki-ng and extend the interop with zephyr, mynewt and mbed. Hopefully we share a common supported board on which we can make the tests more transparently.
thanks @kYc0o and @miri64 for testing ;)
only 5 tests and we get 100% of tests in RC1!
all interop tests passed!
I tested the arduino-zero/xbee tests for task 4 and while they were successful there sometimes were some initialization issues on the xbee side. I'll try to research those, but I don't see them blocking for the release, as the tasks are just experimental.
thanks for testing!
This issue lists the status of all tests for the Release Candidate 1 of the 2018.10 release.
Specs tested:
Task #01 - CORD Endpoint
Task #02 - Confirmable retries
Task #03 - Block1
Task #04 - Block2
Task #05 - Observe registration and notification