Comments (15)
Test Report
from release-specs.
The 11. Task 05 - GNRC LoRaWAN (Over The Air Activation) [otaa]
failure is probably due to the not so reliable TTN ecosystem. Maybe @jia200x can give it a spin locally to confirm?
from release-specs.
All other automated tests that failed seem to be "experimental" meaning we know they are failing...
from release-specs.
The reporting to matrix is also broken but likely a token issue and not critical for this release.
from release-specs.
@jia200x @leandrolanzieri @MichelRottleuthner or I can run some of the interop tests, specifically the one with contiki... I will need to doing in 2 weeks though as next week I am not available.
from release-specs.
The RIOT based tests that were run on boards have the following results:
- iotlab-m3 fails libschc, a known flakey issue
- nrf52dk
tests/sys/event_wait_timeout_ztimer
andtests/sys/xtimer_overhead
are failing and should be evaluated - nucleo-wl55jc
tests/pkg/edhoc_c
should look into, probably a test or module specific failure as it is many placestests/pkg/libschc
flakeytests/sys/ztimer_overhead
should look into
- samr21-xpro looks like some real failures
- sam34-xpro, some failures but more likely a board configuration issue (or maybe a test config issue)
- b-l072z-lrwan flakey
- b-l475e-iot01a flakey
I would focus some effort on the nucleo-wl55jc and nrf52dk failures first...
from release-specs.
Task #12 - ICMPv6 echo between Border Router with WiFi uplink to named Internet host
success
2023-08-01 23:49:29,383 # ifconfig
2023-08-01 23:49:29,388 # Iface 9 HWaddr: 3C:71:BF:9E:13:FD Channel: 6
2023-08-01 23:49:29,391 # L2-PDU:249 MTU:1280 HL:64 RTR
2023-08-01 23:49:29,396 # RTR_ADV 6LO Source address length: 6
2023-08-01 23:49:29,398 # Link type: wireless
2023-08-01 23:49:29,404 # inet6 addr: fe80::3e71:bfff:fe9e:13fd scope: link VAL
2023-08-01 23:49:29,411 # inet6 addr: 2001:9e8:1429:35ff:3e71:bfff:fe9e:13fd scope: global VAL
2023-08-01 23:49:29,414 # inet6 group: ff02::2
2023-08-01 23:49:29,417 # inet6 group: ff02::1
2023-08-01 23:49:29,420 # inet6 group: ff02::1:ff9e:13fd
2023-08-01 23:49:29,421 #
2023-08-01 23:49:29,426 # Iface 10 HWaddr: 3C:71:BF:9E:13:FC Channel: 6 Link: up
2023-08-01 23:49:29,430 # L2-PDU:1500 MTU:1492 HL:255 RTR
2023-08-01 23:49:29,433 # Source address length: 6
2023-08-01 23:49:29,436 # Link type: wireless
2023-08-01 23:49:29,442 # inet6 addr: fe80::3e71:bfff:fe9e:13fc scope: link VAL
2023-08-01 23:49:29,449 # inet6 addr: 2001:9e8:1429:3500:3e71:bfff:fe9e:13fc scope: global VAL
2023-08-01 23:49:29,451 # inet6 group: ff02::2
2023-08-01 23:49:29,454 # inet6 group: ff02::1
2023-08-01 23:49:29,458 # inet6 group: ff02::1:ff9e:13fc
2023-08-01 23:49:29,459 #
> ping 2600::
2023-08-01 23:50:09,095 # ping 2600::
2023-08-01 23:50:09,317 # 12 bytes from 2600::: icmp_seq=0 ttl=52 time=216.761 ms
2023-08-01 23:50:10,333 # 12 bytes from 2600::: icmp_seq=1 ttl=52 time=233.365 ms
2023-08-01 23:50:11,255 # 12 bytes from 2600::: icmp_seq=2 ttl=52 time=154.592 ms
2023-08-01 23:50:11,255 #
2023-08-01 23:50:11,257 # --- 2600:: PING statistics ---
2023-08-01 23:50:11,262 # 3 packets transmitted, 3 packets received, 0% packet loss
2023-08-01 23:50:11,266 # round-trip min/avg/max = 154.592/201.572/233.365 ms
> ping riot-os.org
2023-08-01 23:50:13,086 # ping riot-os.org
2023-08-01 23:50:13,353 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=0 ttl=58 time=48.372 ms
2023-08-01 23:50:14,351 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=1 ttl=58 time=46.811 ms
2023-08-01 23:50:15,354 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=2 ttl=58 time=49.394 ms
2023-08-01 23:50:15,354 #
2023-08-01 23:50:15,357 # --- riot-os.org PING statistics ---
2023-08-01 23:50:15,362 # 3 packets transmitted, 3 packets received, 0% packet loss
2023-08-01 23:50:15,366 # round-trip min/avg/max = 46.811/48.192/49.394 ms
Task #13 - ICMPv6 echo between ESP and named Internet host through RIOT BR with 6LowPAN
success
2023-08-01 23:50:21,531 # Iface 11 HWaddr: 82:7D:3A:7F:E0:1D Channel: 6
2023-08-01 23:50:21,534 # L2-PDU:249 MTU:1280 HL:64 RTR
2023-08-01 23:50:21,539 # RTR_ADV 6LO Source address length: 6
2023-08-01 23:50:21,542 # Link type: wireless
2023-08-01 23:50:21,548 # inet6 addr: fe80::807d:3aff:fe7f:e01d scope: link VAL
2023-08-01 23:50:21,556 # inet6 addr: 2001:9e8:1429:35ff:807d:3aff:fe7f:e01d scope: global VAL
2023-08-01 23:50:21,557 # inet6 group: ff02::2
2023-08-01 23:50:21,560 # inet6 group: ff02::1
2023-08-01 23:50:21,564 # inet6 group: ff02::1:ff7f:e01d
2023-08-01 23:50:21,567 # inet6 group: ff02::1a
2023-08-01 23:50:21,568 #
2023-08-01 23:50:21,570 # Statistics for Layer 2
2023-08-01 23:50:21,573 # RX packets 0 bytes 0
2023-08-01 23:50:21,578 # TX packets 0 (Multicast: 0) bytes 148
2023-08-01 23:50:21,581 # TX succeeded 2 errors 0
2023-08-01 23:50:21,584 # Statistics for IPv6
2023-08-01 23:50:21,587 # RX packets 2 bytes 240
2023-08-01 23:50:21,592 # TX packets 4 (Multicast: 3) bytes 250
2023-08-01 23:50:21,595 # TX succeeded 4 errors 0
2023-08-01 23:50:21,595 #
> ping 2600::
2023-08-01 23:50:29,247 # ping 2600::
2023-08-01 23:50:29,489 # 12 bytes from 2600::: icmp_seq=0 ttl=51 time=234.960 ms
2023-08-01 23:50:30,413 # 12 bytes from 2600::: icmp_seq=1 ttl=51 time=158.848 ms
2023-08-01 23:50:31,437 # 12 bytes from 2600::: icmp_seq=2 ttl=51 time=183.528 ms
2023-08-01 23:50:31,437 #
2023-08-01 23:50:31,440 # --- 2600:: PING statistics ---
2023-08-01 23:50:31,445 # 3 packets transmitted, 3 packets received, 0% packet loss
2023-08-01 23:50:31,450 # round-trip min/avg/max = 158.848/192.445/234.960 ms
> ping riot-os.org
2023-08-01 23:50:32,240 # ping riot-os.org
2023-08-01 23:50:32,314 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=0 ttl=57 time=45.459 ms
2023-08-01 23:50:33,318 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=1 ttl=57 time=49.158 ms
2023-08-01 23:50:34,316 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=2 ttl=57 time=46.856 ms
2023-08-01 23:50:34,316 #
2023-08-01 23:50:34,319 # --- riot-os.org PING statistics ---
2023-08-01 23:50:34,324 # 3 packets transmitted, 3 packets received, 0% packet loss
2023-08-01 23:50:34,328 # round-trip min/avg/max = 45.459/47.157/49.158 ms
from release-specs.
Task #03 - UDP exchange between iotlab-m3 and Contiki (with samr21-xpro
)
success
samr21-xpro
> udp send fe80::0212:4b00:0422:9db8 3000 64
2023-08-02 12:54:08,639 # udp send fe80::0212:4b00:0422:9db8 3000 64
2023-08-02 12:54:08,646 # Success: send 64 byte to [fe80::0212:4b00:0422:9db8]:3000
2023-08-02 12:54:08,655 # Packets received: 5
cc2538dk
2023-08-02 12:54:08,657 # 64 bytes from [fe80::204:2519:1801:bd47]:3000
from release-specs.
The zephyr tests are still a bit funky. I was able to ping and get responses but the zephyr node crashes at some point. I had to do a bunch of cuts in the config of the samr of the zephyr node to make it fit so maybe I took too much. It seems like a zephyr usage issue rather than RIOT though.
from release-specs.
Did we ever report the issue to the Zephyr issue tracker?
from release-specs.
I did not but @jia200x said it was just a buffer problem. I think the solution would be using a board with more resources for the release test, such as an nrf board.
from release-specs.
You can also free up more RAM if you disable things like shell history - still it shouldn't outright crash if it runs out of memory for incoming packets
from release-specs.
I already did try to strip away things from the shell history and a bunch of seemingly unrelated features. I also didn't get any panics or so, the whole things just stop talking. I really haven't spend much time with zephyr and probably there are many things that could be done to help this.
Do you think it would actually be RIOT causing this crash?
from release-specs.
Do you think it would actually be RIOT causing this crash?
Even if this were the case, the bug would still be in the network stack that crashes upon receiving such packet over the network.
from release-specs.
I think this one is finished 😄
from release-specs.
Related Issues (20)
- Release 2022.07 - RC4 HOT 25
- Release 2022.10 - RC1 HOT 7
- Release 2022.10 - RC2 HOT 9
- Release 2022.10 - RC3 HOT 18
- Release 2023.01 - RC1 HOT 3
- Release 2023.01 - RC2 HOT 2
- Release 2023.01 - RC3 HOT 14
- 08 - Task 11: Building zephyr on atsamr21_xpro not possible HOT 4
- Release 2023.04 - RC1 HOT 12
- [RFC] Restructure/update Release Specs HOT 2
- Release 2023.04 - RC2 HOT 5
- Release 2023.04 - RC3 HOT 3
- Release 2023.10 - RC1 HOT 11
- Release 2023.10 - RC2 HOT 5
- Release 2023.10 - RC3 HOT 4
- Release 2024.01 - RC1 HOT 4
- Release 2024.01 - RC2 HOT 17
- Release 2024.04 - RC1 HOT 12
- Release 2024.04 - RC2 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-specs.