Closed MrKevinWeiss closed 5 years ago
(forgot the large payload, so it is a rerun of 5, but :woman_shrugging: you managed to run it yourself :-))
@fjmolinas Very nice, thanks (is that for RC1 or devel)?
@MrKevinWeiss Oh I actually had checkout 2019.07-branch. Should I remove the checks then (they where all failing for RC1)? I guess I'm a little bit lost with the procedure..
Well it is good to verify fixes fix that. I think it is fine. I will try to create RC2 and they should be retested there.
@MrKevinWeiss do all tests need to be re-run for every RC?
ideally yes. Practically it is a judgement call. If the only difference in an RC is, say a fix to a board gpio then I would be ok skipping it but if there was a fix in gnrc and in, say, msg handling then I probably would want to make sure that all tests are run again. Just so the stomp out one bug then two more appear phenomenon doesn't happen.
10-icmpv6-error Task 10 run riot-release-10-10.py with the following params:
sudo python3 riot-release-10-10.py tapbr0 "fe80::7436:19ff:fe35:4950" "fe80::5c35:feff:fe40:d09a" "76:36:19:35:49:50" "5e:35:fe:40:d0:9a"
No errors
2-tests Task 02 - Subset of tests on iotlab-m3 PASSED?
ERROR:iotlab-m3:Tests failed: 5
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
EDIT: re-ran the gnrc ones needing sudo with sudo, and they are passing.
02-1 passed but I needed to manually do sudo from some tests and run BUILD_IN_DOCKER=1 for cpp tests (since it isn't setup)
~@fjmolinas odd to put those links in~ <= ahh copy and paste. I guess the gnrc stuff needs sudo and I the fatfs needs an sd card or something special on the sd card... It is a pretty special case.
It says Tests failed: 5
with 4 tests listed.
arrays start at 2
It says Tests failed: 5 with 4 tests listed.
Yep I was implementing a python test script for 11-lorawan
and when checking out the RC1 branch it didn't get removed. I didn't want to re-run the tests because of that.
@fjmolinas odd to put those links in <= ahh copy and paste. I guess the gnrc stuff needs sudo and I the fatfs needs an sd card or something special on the sd card... It is a pretty special case.
I'll mark as passing sin I re-ran those 3 with sudo and they are passing. Running for samr21 now..
99-compile-and-test-one-board Task #01 - Run tests on different hardwares
I could leave it running over night for 4 boards, any preferences? @MrKevinWeiss
Oh very nice @fjmolinas I really appreciate the help. I would say choose ones that don't have known flashing or term problems and different cpus.
I can run the tests again on arduino-mega2560 cc2650-launchpad frdm-k64f frdm-kw41z msba2 mulle nrf52dk nucleo-f103rb pba-d-01-kw2x sltb001a stm32f3discovery
As said in https://github.com/RIOT-OS/Release-Specs/issues/128#issuecomment-511451764 01/task2 and 01/task3 worked. The 01/Task4 works on the 2019.07-branch
as https://github.com/RIOT-OS/RIOT/pull/11858 was merged.
But I cannot tick the checkbox.
2-tests Task 03 - Subset of tests on samr21-xpro PASSED
ERROR:samr21-xpro:Tests failed: 4
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
The first 3 succeed when running with sudo
@fjmolinas: @aabadie should have one of those lying around: https://doc.riot-os.org/group__drivers__io1__xplained.html (he wrote the driver). Maybe the fourth succeeds with that.
interop 8 task 02: works with link local and global (ULA) addresses
interop 8 task 04: works bidirectional when using CFLAGS += -DGNRC_IPV6_NIB_CONF_SLAAC=1
. It also works from Internet host to RIOT w/o that flag, but not from RIOT to Internet host. The latter is weird because it means that source address selection (or exclusion) is different when RIOT is initial sender or only responder - though I assume, that when responding RIOT just switches src and dst addresses w/o checking validity of its own source address.
Closing in favor of #133
The arduino-mega2560
did not run due to crap hardware.
#### cc2650-launchpad/failuresummary.md
Failures during test:
- [tests/cond_order](tests/cond_order/test.failed)
- [tests/driver_grove_ledbar](tests/driver_grove_ledbar/test.failed)
- [tests/driver_my9221](tests/driver_my9221/test.failed)
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/periph_timer](tests/periph_timer/test.failed)
- [tests/ps_schedstatistics](tests/ps_schedstatistics/test.failed)
#### frdm-k64f/failuresummary.md
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/periph_timer](tests/periph_timer/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/ps_schedstatistics](tests/ps_schedstatistics/test.failed)
#### frdm-kw41z/failuresummary.md
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/ps_schedstatistics](tests/ps_schedstatistics/test.failed)
- [tests/thread_flags](tests/thread_flags/test.failed)
- [tests/unittests](tests/unittests/test.failed)
- [tests/xtimer_periodic_wakeup](tests/xtimer_periodic_wakeup/test.failed)
- [tests/xtimer_usleep](tests/xtimer_usleep/test.failed)
#### msba2/failuresummary.md
Failures during test:
- [tests/driver_grove_ledbar](tests/driver_grove_ledbar/test.failed)
- [tests/driver_my9221](tests/driver_my9221/test.failed)
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sixlowpan](tests/gnrc_sixlowpan/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/libfixmath](tests/libfixmath/test.failed)
- [tests/libfixmath_unittests](tests/libfixmath_unittests/test.failed)
- [tests/lwip_sock_tcp](tests/lwip_sock_tcp/test.failed)
- [tests/periph_rtc](tests/periph_rtc/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/pkg_libcose](tests/pkg_libcose/test.failed)
- [tests/pkg_qdsa](tests/pkg_qdsa/test.failed)
- [tests/pkg_relic](tests/pkg_relic/test.failed)
- [tests/pkg_tweetnacl](tests/pkg_tweetnacl/test.failed)
- [tests/pthread_tls](tests/pthread_tls/test.failed)
- [tests/unittests](tests/unittests/test.failed)
- [tests/xtimer_periodic_wakeup](tests/xtimer_periodic_wakeup/test.failed)
#### mulle/failuresummary.md
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/periph_timer](tests/periph_timer/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/pkg_littlefs](tests/pkg_littlefs/test.failed)
- [tests/pkg_spiffs](tests/pkg_spiffs/test.failed)
- [tests/shell](tests/shell/test.failed)
#### nrf52dk/failuresummary.md
Failures during compilation:
- [tests/mcuboot](tests/mcuboot/compilation.failed)
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
#### nucleo-f103rb/failuresummary.md
Failures during test:
- [tests/driver_grove_ledbar](tests/driver_grove_ledbar/test.failed)
- [tests/driver_hd44780](tests/driver_hd44780/test.failed)
- [tests/driver_my9221](tests/driver_my9221/test.failed)
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/xtimer_periodic_wakeup](tests/xtimer_periodic_wakeup/test.failed)
- [tests/xtimer_usleep_short](tests/xtimer_usleep_short/test.failed)
#### pba-d-01-kw2x/failuresummary.md
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/ps_schedstatistics](tests/ps_schedstatistics/test.failed)
#### sltb001a/failuresummary.md
Failures during test:
- [tests/embunit](tests/embunit/test.failed)
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/periph_gpio](tests/periph_gpio/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
- [tests/ps_schedstatistics](tests/ps_schedstatistics/test.failed)
- [tests/xtimer_periodic_wakeup](tests/xtimer_periodic_wakeup/test.failed)
#### stm32f3discovery/failuresummary.md
Failures during test:
- [tests/gnrc_ipv6_ext](tests/gnrc_ipv6_ext/test.failed)
- [tests/gnrc_rpl_srh](tests/gnrc_rpl_srh/test.failed)
- [tests/gnrc_sock_dns](tests/gnrc_sock_dns/test.failed)
- [tests/pkg_fatfs_vfs](tests/pkg_fatfs_vfs/test.failed)
interop 8 task 04: works bidirectional when using
CFLAGS += -DGNRC_IPV6_NIB_CONF_SLAAC=1
. It also works from Internet host to RIOT w/o that flag, but not from RIOT to Internet host. The latter is weird because it means that source address selection (or exclusion) is different when RIOT is initial sender or only responder - though I assume, that when responding RIOT just switches src and dst addresses w/o checking validity of its own source address.
It's not weird, because for ping reply the source address is known (the one the sender of the echo request used as destination address), so that is used. If you are the sender of an echo request it has to be determined first, so source address selection is triggered.
mhm, yeah sure the source address is known (as I wrote: just switch src and dst addresses) - however, it might be invalid and hence should not be used?!
You are right. A check in gnrc_ipv6
is needed for that. However, this is a minor issue and should not be blocking for the release.
However, this is a minor issue and should not be blocking for the release.
:relieved:
This issue lists the status of all tests for the Release Candidate 1 of the 2019.07 release.
Specs tested: