-
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.07 - RC4 #258
Comments
With backports for compiler errors that would show up on the user's side out of the way (RIOT-OS/RIOT#18488, RIOT-OS/RIOT#18485), I think this should be the final one. RIOT-OS/RIOT#18479 will go into "known issues" with yet to be decided scope. @jia200x please run the missing LoRA test (ABP is not automated); and IIRC you also have access to the 08-interop tests? |
The ABP test does not run on TTN (see RIOT-OS/RIOT#16962). |
Native tests largely passed like in #257 (comment) -- but a new pkg has triggered static test failures in GCC. There is RIOT-OS/RIOT#18508 reported now, but considering how that'd stretch things out I'm putting this on "known issues". (While this is conceptually similar to the CCN-lite use-after-free for which I did go through another RC, the difference is that there it was UB on old compilers, and here it's just access out of bounds declared in the function argument, which AIU is not UB on its own in C). Thus ticking the native box. |
08. Task 11 - UDP exchange between iotlab-m3 and Zephyr - PASS
I observed a couple of missing echoes from the zephyr node (fixed by a reboot of it), but the Zephyr would receive the RIOT packet. |
08-interop. Task #4 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN - PASS
|
08-interop. Task #5 - ICMPv6 echo between iotlab-m3 and Internet host through RIOT border router - PASS
|
08-interop. Task #6 - UDP between iotlab-m3 and Internet host through RIOT border router - PASS
|
08-interop. Task #7 - UDP between iotlab-m3 and Internet host through RIOT border router (200b payload) - PASS
|
08-interop. Task #2 - ICMPv6 echo between iotlab-m3 and Linux with 6LowPAN - PASS
|
08-interop. Task #3 - UDP exchange between iotlab-m3 and Contiki - PASS
|
I ran all interest tests I could. Could someone run the ones with Wifi and ESP? |
On Wed, Aug 24, 2022 at 08:25:46AM -0700, José Alamos wrote:
I ran all interest tests I could. Could someone run the ones with Wifi and ESP?
@gschorcht, could you help here maybe?
|
Ran compile-and-test locally with tests on IoT-Lab for iotlab-m3 and samr21; largely as in the last test:
|
Task #12 - ICMPv6 echo between Border Router with WiFi uplink to named Internet hostpassed (esp32-wroom-32)
Task #13 - ICMPv6 echo between ESP and named Internet host through Linux with 6LowPANpassed (esp8266-esp-12x)
Ping from Linux also works
Unfortunately the esp8266 hangs very quickly after being exposed to the local network - but this is not a new issue. |
Ran a bunch of other examples to satisfy 99-compile-and-test-one-board:
|
The remaining ticks are all either
Looking good; unless the LoRaWAN example keeps breaking, or someone stumbles over something critical, this will be it, once the release notes are through. |
Can be, but is flaky, see #255.
Probably should be marked as flaky as well. |
It failed again, but it worked in RC3 without any relevant changes in that area, so I'd consider this flaky based on the above. Thus, all tests either passed or are expected to (sometimes) fail; it's only the release notes now (which I'd let gather feedback over the weekend). |
yeah, during testing #255, @jia200x and I noticed, that if the lorawan nodes on the testbed "decide" to not to work, they will stay that way for a while :-/... so maybe it doesn't even make sense to mark the test as flaky, in the |
Yup... it's because of iotlab nodes randomly disconnecting. This test always succeeds when ran locally. |
Unfortunately not, I'm on vacation. Although I have some hardware with me, I don't have the required WiFi infrastructure here. But, I have use WiFi so often in last month that I'm convinced that it works in 2022.07. Maybe @benpicco might confirm. |
I already ran the test - #258 (comment) |
Ah ok, I see. Sorry for the noise, a smartphone is obviously not a good choice for checking emails, following links in emails, and keeping a track of what's going on.. |
Should have been closed with the release. Thanks everyone for helping out! |
This issue lists the status of all tests for the Release Candidate 4 of the 2022.07 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: