-
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 2018.10 - RC2 #81
Comments
@kb2ma do you have time to re-run the |
No problem, @jia200x. I'll should get to it by Wednesday morning. |
Awesome! Thank you so much! |
waiting for 01/01. Unittests pass in all variants |
I don't have access to a remote, so 4.5 and 4.6 needs to be done by someone else. |
We can run it here at HAW |
Nothing interesting to report for task 4. |
GNRC - emb6 - lwip triade works as expected in the interop tests |
09-coap works as expected. |
Native tests:
I think we should implement the classic |
FYI, @bergzand found a serious bug in RIOT-OS/RIOT#10246 (comment). Luckily in its current version RIOT-OS/RIOT#10246 fixes that (though very ugly, but later reversible). |
Output of compile test:
The |
I ran some I will try running it for the boards supporting llvm and do a report. |
I'm doing a fix for the native reports as we speak. @jia200x do we do another release candidate for all those last minute GNRC stuff? |
See RIOT-OS/RIOT#10350. |
Yes. Also for the latest fixes |
Unfortunately I did not have time to run and analyze them before the week-end. |
Who tested 8.6 and 8.7 because the RIOT border router on |
I tested it. It didn't crash in any of the RC. Let me re-check in any case |
(It also crashes on RC2, I checked) |
All-clear: it was the broken samr21-xpro I was using ^^" |
Already in RC3 |
This issue lists the status of all tests for the Release Candidate 2 of the 2018.10 release.
Specs tested:
1% packet loss
0.5% packet loss
Task #01 - CORD Endpoint
Task #02 - Confirmable retries
Task #03 - Block1
Task #04 - Block2
Task #05 - Observe registration and notification
The text was updated successfully, but these errors were encountered: