-
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
Release 2024.01 - RC2 #303
Comments
Test Task #02 - ICMPv6 echo between iotlab-m3 and Linux with 6LowPAN: PASS
|
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN PASS
|
Test Report
|
Task #06 - UDP between iotlab-m3 and Internet host through RIOT border router PASS Task #07 - UDP between iotlab-m3 and Internet host through RIOT border router (200b payload) PASS
|
Task #11 - UDP exchange between iotlab-m3 and Zephyr iotlab-m3
samr21-xpro
|
I will do the two ESP tests |
If nothing else goes wrong then only: and are left and we can release! |
I'm on it! |
So, ESP task 12:
this works. I had to cheat a bit by adding |
Wait, the second interface doesn't get a global IP. I think my home network does do prefix delegation, at least my OpenWRT does claim to do that. |
Task #06 - GNRC LoRaWAN (ABP) - PASSES* I couldn't test downlink because Chirpstack is also replying with downlink frames in Port 0, which requests the node to change transmission settings and won't send additional data until it takes effect. So we cannot test this in ABP unless we implement the missing FOpts. In any case, I wouldn't worry that much. The downlink feature is decoupled from the joining logic and it was already tested in the OTAA test.
|
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN PASSES
|
I opened an issue regarding the failing ESP test: RIOT-OS/RIOT#20349 I think that the test would have worked if I didn't had a chain of two routers. My current setup is that I use a cheap FritzBox with a VDSL2 modem but no WiFi capabilities (802.11g and 2.4 GHz only IMO "no WiFi capabilities) and an OpenWrt box with WiFi behind that (802.11 ax dual-band). As a result the OpenWrt only has a smaller prefix to delegate. My guess is that RIOT's DHCPv6 is asking for a prefix longer than what the OpenWrt can or is willing to offer. So no regression, but an issue that always has been there. Should IMO not block the release and is documented via the issue. |
Perfect... I think we can release as is and just backport RIOT-OS/RIOT#20348 to the release branch and it will be included with any point releases in the future. |
Release is complete! |
This issue lists the status of all tests for the Release Candidate 2 of the 2024.01 release.
Specs tested:
The text was updated successfully, but these errors were encountered: