Release 2019.10 - RC1 #140
Labels
Comments
|
Ran 02-tests/task-01. Found failure on tests/gnrc_rpl_srh. Posted RIOT-OS/RIOT#12436. |
|
This is my first time running many of these tests, so please bear with my questions. The instructions for spec 02-tests say to run tests/compile_and_test_for_board. The readme for that test says that it runs only automated tests. For the purpose of 02-tests/01, is it necessary to run any/all manual tests? If so, is there an easy way to determine which tests are expected to be run this way? For 02-test, tasks 02 and 03: How does one decide on a reasonable subset of tests? |
|
For 01-ci/01, I ran a few of these. However, I am missing some toolchains and the tests look like they will take a significant amount of time to run. Looking at the last release, maybe some Docker image is the way to go. If someone has an environment set up already for this, that would be helpful. |
|
I 'll ran task 99 on the following
|
11-lorawan Task 1 Passes
|
|
Ran tasks 01-2, 01-3 and 01-4 with success: 01-ci Task2: Unittests on native
|
11-lorawan Task 4 Passes |
11-lorawan Task 2 Passes
|
11-lorawan Task 3 Passes
|
|
I ran task 99 on Except some local machine handling, I had to disable The local configuration is explained in paper-ci and points to the aggregated I will do a readable summary in this comment. Tests on All tests are currently run even the cc2650-launchpadek-lm4f120xl
esp32-wroom-32129 test failed. But most are due to not being supported by RIOT testing method. frdm-k64ffrdm-kw41zmsba2
nrf52dknucleo-f103rbpba-d-01-kw2xsltb001astm32f3discoveryNo failures. (Except in blacklisted tests) |
|
I will run the automated tests on |
|
@smlng Can you take care of some of the interop tests (at least the raspi ones)? |
|
@MrKevinWeiss sure! As long as you it merge on the timer test 😉 |
My machine crashed, it's is a shitty machine but I'll have to find a replacement or re-start the tests. |
07-multi-hop
|
|
The automated tests on iotlab-m3samr21-xpro |
8-interop Task 3 Passes in RC1
|
8-interop Task 8 Passes in RC1
|
8-interop Task 9 Passes in RC1
|
8-interop Task 10 Passes in RC1
|
@cladmi, so this is 02-tests for those boards? Are the riotboot failures known issues, or do we need to report/investigate? |
I opened #12446 to address this, it is a known issue. |
9-Coap Task 1 passes |
Got it, thanks. I updated the issue comment. |
|
@aabadie, thanks for running 01-ci/01. What was the outcome? |
9-Coap Task 2 Passes
|
@cladmi, I compared the results to those reported for 2019.07. I see a lot of repeat failures, but I also notice new issues:
Are the failures with riotboot addressed by RIOT-OS/RIOT#12446? Did you test ek-lm4f120xl for 2019.07? Are the shell and periph_rtc failures concerning? |
09-Coap Task 3 Passes
|
|
@jia200x, any results on 08-interop/06,07? We're close to creation of an RC2, and would love to make one pass through all of the tests. Thanks for all you have done so far! |
We should wait for RIOT-OS/RIOT#12502 and RIOT-OS/RIOT#12512 [edit]anyway[/edit] to be backported first, otherwise we need definitely an RC3. |
I can also have a look at the remaining interops on Monday. |
Thanks for advice, and I agree completely. Just trying to keep the pipeline filled ;-) |
|
I just deleted a comment from a few minutes ago about 04/task-10. This was a known failure addressed with backport RIOT-OS/RIOT#12434. We'll check that again with RC2. |
|
The |
|
I also know the usb to serial interface of the |
Task 8.2 (compiled with (edit: replaced with results from RC1, before I was on the current 2019.10-branch; also added return the other way around, ping Linux to RIOT) |
|
The backport for #12502 (#12524) is merged, and I just ACKed the backport for #12512 (#12521). After that merge, if @MrKevinWeiss gives the OK on the nrf52 serial test, we should be ready for RC2 AFAICT. @miri64 or anyone, any other concerns before RC2? |
|
Task 8.4: On Raspberry Pi: sudo ip addr add 2001:db8::1/64 dev eth0On RIOT |
|
01-ci - Task 01 is fixed by RIOT-OS/RIOT#12524. |
|
Task 8.5: On my Linux Host: On RIOT: |
Thanks for working through that, @aabadie! |
No not to my knowledge. Just testing the UDP interops |
|
So far the tests are passing the only issue I have with the nrf52dk is but it is on the Pi so I don't know if that is a real problem. |
|
Task 8.6: On Linux: On RIOT: |
|
shell tests passes on the nrf52dk |
|
Task 8.7: On Linux: On RIOT: => Spec 08 Passes overall. |
Can reproduce on my Ubuntu machine. However, the README mentions this requirement. How this is solved on the CI without Docker having this requirement pulled in, I don't know. Maybe @fjmolinas or @kaspar030 can give some insight. |
The build container does pull this in: |
|
@miri64 @MrKevinWeiss maybe you need to do |
|
Thanks, everyone. I plan to create RC2 later today. |
|
BTW, there is an issue with |
Ah, overlooked that, because I thought the file was ordered alphabetical ^^" |
|
Closing in favor of #142 |
|
My results from Spec 03, Task 04 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue lists the status of all tests for the Release Candidate 1 of the 2019.10 release.
Specs tested:
The text was updated successfully, but these errors were encountered: