-
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 2019.07 - RC1 #128
Comments
As tested just before the RC1 @cladmi found the following issues on the board Board Test Results
|
For boards failing with
For:
I think they fail because they need to be run with sudo (because of ethos). @kaspar030 has done some work with the CI to enable running ethos without sudo (RIOT-OS/RIOT#11816 is one of the PR's), we needed and have been using this to tests RIOT-OS/RIOT#11818. |
Compared to the last RC1 no knew bugs seem to be introduced. |
Indeed. The test are the result of running I do not consider It is stupid automated testing :) The test were run using
I checked the output and I also had other issues on my test machine:
Despite being installed, The test result should not change but the output should. |
I will run the task
I can also run the automated test suite on different boards as I already did. |
@kb2ma Would you be interested in testing task 09-coap by chance? |
Please run the failing sudo tests regardless of whether there will be execution without root in the CI or not (since that requires some bootstrapping for scapy, rather not for this release), manually. That is the point why they are included in the release specs ;-) |
Yes, happy to run 09-coap. |
@leandrolanzieri, I don't want to interrupt if you plan to continue with 09-coap. Let me know. |
@kb2ma sorry, yes, almost done with them |
Everything looks good for 09-coap and 06-single-hop-udp |
07-Multihop had 0% packet loss and no packet buff problems!
|
05
|
For the
|
Hmm it seems that I am have some problems on Task #02 - ICMPv6 echo unicast addresess on iotlab-m3 (default route) Can someone confirm? |
I did a run of
I used some It currently reported ~130 in RIOT (including deprecation warnings for https://ci-ilab.imp.fu-berlin.de/job/RIOT%20scan-build-analyze/16/riot_scan_build/ |
It's working for me, 1% Packet Loss |
In theory, also all the non automated tests should also be executed. From RIOT-OS/RIOT#11821 |
Yup. This is unfortunately not a matter of just installing scapy, as scapy wants to open a raw socket, which only root can do. |
Will fix very soon (but not in a backportable state I fear) |
There might also be a workaround using ambient capabilities: https://stackoverflow.com/a/47982075/5910429 |
There is a TUN/TAP-Wrapper hidden inside |
(all our scapy raw sockets use either TUN or TAP interfaces so far, so if they have user permissions granted at creation—see |
Totally agreed! And let me know if I can help. (I just stumbled over the workaround and wanted to share it.) |
So I did 05-task4 and with 0% packetloss |
I am getting some pretty high packet loss for 04-Task #1 - ICMPv6 link-local echo with iotlab-m3 only when running locally, between 10% and 50%. I was using the tests/gnrc_udp to test. @miri64, @cgundogan, any ideas? @PeterKietzmann said it could be the Hamburg air or maybe it is our M3 boards that have some issue, maybe floating pins or something? I will note the the USB is a little bit sensitive to position. |
If it works on IoT-LAB (have you tried different sites?) or Varduz, it seems to be the Hamburg air. We had problmes in the past where tests over radio conducted at HAW Hamburg failed while they worked at other places. Maybe there is something jamming the spectrum in your building. |
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) |
|
It says |
arrays start at 2 |
Yep I was implementing a python test script for |
I'll mark as passing sin I re-ran those 3 with sudo and they are passing. Running for samr21 now.. |
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 |
8-interop Task 10 Passes in RC1
|
As said in #128 (comment) 01/task2 and 01/task3 worked. The 01/Task4 works on the But I cannot tick the checkbox. |
8-interop Task 9 Passes in RC1
|
8-interop Task 8 Passes in RC1
|
2-tests Task 03 - Subset of tests on samr21-xpro PASSED
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 |
Closing in favor of #133 |
The
|
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 |
😌 |
This issue lists the status of all tests for the Release Candidate 1 of the 2019.07 release.
Specs tested:
The text was updated successfully, but these errors were encountered: