-
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 2022.04 - RC6 #247
Comments
@MrKevinWeiss, @benpicco, @fjmolinas, @bergzand, could you help with the interop tests? |
Sure, I can give it a try tomorrow morning. I thought some were already done by @jia200x. Did you want all (possible) one rerun? |
I'm not aware of any previous runs. |
UDP exchange between iotlab-m3 and Contiki (:heavy_check_mark: PASS)riot
contiki
|
Note that the Zephyr node crashes after the echo (we assume it is not riots fault), tested on the old version of zephyr and the new version. UDP exchange between iotlab-m3 and Zephyr (Mostly PASS)
|
|
We should probably open an issue for that |
A bit off-topic but the iot-lab team started to port Zephyr to the iotlab-m3. This WIP work is in an iot-lab fork. Basic stuff are working but not the radio... If one day it works, it will be possible to run the interop between 2 iotlab-m3 (1 running RIOT, the other running Zephyr) 😃 |
Just to be clear, also Zephyr board will randomly crash after some time (after about 10 seconds). previous 1 2 3 runs seemed to have varied results and I remember these issues always being present. @leandrolanzieri had to play around with the buffer sizes to make the firmware fit which may have contributed to it (or not). Either way I would say "exists in previous releases" or something to that effect. |
All {RIOT, RPI}-border router test passed. |
all LoRaWAN test passed. https://github.com/RIOT-OS/Release-Specs/blob/faafe7bcbaf13751b9b07cf5490a7bead13faa27/11-lorawan/README.md#task-06---gnrc-lorawan-abp should be skipped due to RIOT-OS/RIOT#16962 |
@jia200x, do you know what's up with https://github.com/RIOT-OS/Release-Specs/blob/faafe7bcbaf13751b9b07cf5490a7bead13faa27/11-lorawan/README.md#task-03---abp-join-procedure? It failed. Or is it one of the flaky tests, @fjmolinas mentioned? |
I ran 62 random tests on samr21-xpro and got 62 test.success files. |
Running the unit-tests on native again with
I thought that |
Murdock honors
The compile failures, I don't know.
|
Interestingly the compile errors only occur when I build them with
The tests build just fine when built without docker. |
Okay, two other tests failed because So, basically all tests that should succeed now, except for
@miri64, do you have an idea here? |
The python tests script uses "scapy", maybe that needs to be installed? |
Task #12 - ICMPv6 echo between Border Router with WiFi uplink to named Internet host - broken
board is stuck in a boot loop same on 2022.01-branch
This is with |
I ran the semtech lorawan ABP test manually and passed |
Hm, scapy was installed already. Does the test work on your machine? |
Yes, |
So, networking on esp32 is apparently broken!? I tend to call this a blocker for the release. |
Good enough for me. :) |
Found the issue on esp32: 08196603030b735dff4d1569b850ea720d6d5c38 is the first bad commit
cpu/native/Kconfig | 1 - With that commit reverted:
|
Maybe something went wrong in the socket initialization? But not sure. Happy that it seem to have resolved itself :D |
Closing in favor of #248 |
This issue lists the status of all tests for the Release Candidate 6 of the 2022.04 release.
Specs tested:
Task Release 2015.12 - pre-RC1 #9 - deprecatedTask Release 2015.12 - RC1 #10 - deprecatedThe text was updated successfully, but these errors were encountered: