Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Release 2023.07 - RC5 #286

Closed
56 of 86 tasks
benpicco opened this issue Jul 17, 2023 · 15 comments
Closed
56 of 86 tasks

Release 2023.07 - RC5 #286

benpicco opened this issue Jul 17, 2023 · 15 comments
Labels
help wanted

Comments

@benpicco
Copy link
Contributor

benpicco commented Jul 17, 2023 •
edited by MrKevinWeiss
Loading

This issue lists the status of all tests for the Release Candidate 5 of the 2023.07 release.

Specs tested:
@riot-ci
Copy link

riot-ci commented Jul 17, 2023 •
edited
Loading

Test Report

Task Outcome
✔ 01. Task 02 - Unittests on native PASSED
✔ 01. Task 03 - Unittests on native separated [tests-analog_util] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-base64] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bcd] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bhp_event] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bhp_msg] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bitfield] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bloom] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-bluetil] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-checksum] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-chunked_ringbuffer] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-clif] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-coding] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-color] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-core] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-credman] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-div] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-dns_cache] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ecc] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-fib] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-fib_sr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-fmt] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-frac] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gcoap] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_ipv6] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_ipv6_hdr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_ipv6_nib] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_mac_internal] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_netif_pktq] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_sixlowpan_frag_vrb] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-gnrc_udp] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-hashes] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ieee802154] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-inet_csum] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ipv4_addr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ipv6_addr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ipv6_hdr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-kernel_defines] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-libc] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-luid] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-matstat] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-mtd] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-nanocoap] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-nanocoap_cache] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-netopt] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-netreg] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-phydat] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-pkt] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-pktbuf] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-pktqueue] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-printf_float] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-priority_pktqueue] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-rtc] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-rtt_rtc] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-saul_reg] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-scanf_float] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-seq] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-sht1x] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-sixlowpan] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-sixlowpan_ctx] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-sixlowpan_sfr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-sock_util] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-timex] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-tsrb] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-turo] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-uri_parser] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ut_process] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-uuid] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-vfs] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-zptr] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ztimer64] PASSED
✔ 01. Task 03 - Unittests on native separated [tests-ztimer] PASSED
✔ 01. Task 04 - Unittests on iotlab-m3 PASSED
✔ 03. Task 01 - ICMPv6 multicast echo on native PASSED
✔ 03. Task 02 - ICMPv6 link-local echo on native PASSED
✔ 03. Task 03 - ICMPv6 link-local echo on native (1 hour) PASSED
✔ 03. Task 04 - ICMPv6 stress test on native (1 hour) PASSED
✔ 03. Task 05 - ICMPv6 stress test on native (neighbor cache stress) PASSED
✔ 03. Task 06 - ICMPv6 link-local echo on native (IPv6 fragmentation) PASSED
✔ 04. Task 01 - ICMPv6 link-local echo with iotlab-m3 PASSED
✔ 04. Task 02 - ICMPv6 multicast echo with iotlab-m3/samr21-xpro PASSED
✔ 04. Task 03 - ICMPv6 echo with large payload PASSED
✔ 04. Task 04 - ICMPv6 echo with iotlab-m3/samr21-xpro 15 minutes PASSED
🟡 04. Task 05 (Experimental) - ICMPv6 multicast echo with samr21-xpro/cc2538 [lille] SKIPPED
🟡 04. Task 06 (Experimental)- ICMPv6 link-local echo with samr21-xpro/cc2538 [lille] SKIPPED
🟡 04. Task 07 (Experimental) - ICMPv6 multicast echo with samr21-xpro/zero + xbee SKIPPED
🟡 04. Task 08 (Experimental) - ICMPv6 echo with samr21-xpro/zero + xbee SKIPPED
✔ 04. Task 09 - ICMPv6 stress test on iotlab-m3 PASSED
✔ 04. Task 10 (Experimental) - ICMPv6 echo with large payload (IPv6 fragmentation) PASSED
✔ 04. Task 11 (Experimental) - ICMPv6 stress test on nrf802154 PASSED
✔ 04. Task 12 (Experimental) - ICMPv6 multicast echo with iotlab-m3/nrf802154 PASSED
✔ 04. Task 13 (Experimental) - ICMPv6 link-local echo with iotlab-m3/nrf802154 PASSED
✔ 05. Task 01 - ICMPv6 echo unicast addresess on native (default route) PASSED
✔ 05. Task 02 - ICMPv6 echo unicast addresess on iotlab-m3 (default route) PASSED
✔ 05. Task 03 - ICMPv6 echo unicast addresess on native (specific route) PASSED
✔ 05. Task 04 - ICMPv6 echo unicast addresess on iotlab-m3 (static route) PASSED
✔ 06. Task 01 - UDP on iotlab-m3 PASSED
✔ 06. Task 02 - UDP on iotlab-m3 (UDP port compression) PASSED
✔ 06. Task 03 - UDP on native (non-existent neighbor) PASSED
✔ 06. Task 04 - UDP on iotlab-m3 (non-existent neighbor) PASSED
✔ 06. Task 05 - Empty UDP on native PASSED
✔ 06. Task 06 - Empty UDP on iotlab-m3 PASSED
✔ 07. Task 01 - ICMPv6 echo on iotlab-m3 with three hops (static route) PASSED
✔ 07. Task 02 - UDP on iotlab-m3 with three hops (static route) PASSED
✔ 07. Task 03 - ICMPv6 echo on iotlab-m3 with three hops (RPL route) PASSED
✔ 07. Task 04 - UDP on iotlab-m3 with three hops (RPL route) PASSED
🟡 07. Task 05 (Experimental) - UDP with large payload on iotlab-m3 with three hops (RPL route) SKIPPED
✔ 08. Task 01 - ICMPv6 echo between native and Linux PASSED
✔ 08. Task 08 - UDP between GNRC and lwIP on iotlab-m3 PASSED
✔ 09. Task 01 - CORD Endpoint PASSED
✔ 09. Task 02 - Confirmable retries [False-0] PASSED
✔ 09. Task 02 - Confirmable retries [True-1] PASSED
✔ 09. Task 03 - Block1 PASSED
✔ 09. Task 04 - Block2 PASSED
✔ 09. Task 05 - Observe registration and notification PASSED
✔ 10. Task 01 - Destination unreachable - no route to destination PASSED
✔ 10. Task 02 - Destination unreachable - Beyond scope of source address PASSED
✔ 10. Task 03 - Destination unreachable - address unreachable (target node address) PASSED
✔ 10. Task 04 - Destination unreachable - address unreachable (neighbor cache miss) PASSED
✔ 10. Task 05 - Destination unreachable - port unreachable PASSED
✔ 10. Task 06 - Destination unreachable - port unreachable (large payload) PASSED
✔ 10. Task 07 - Packet too big PASSED
✔ 10. Task 08 - Time exceeded - hop limit exceeded in transit PASSED
✔ 10. Task 09 - Parameter problem - erroneous header field encountered PASSED
✔ 10. Task 10 - IPv6-in-IPv6 encapsulation PASSED
✔ 11. Task 01 - LoRaWAN example PASSED
✔ 11. Task 02 - OTAA join procedure [0] PASSED
✔ 11. Task 02 - OTAA join procedure [5] PASSED
✔ 11. Task 03 - ABP join procedure [0] PASSED
✔ 11. Task 03 - ABP join procedure [3] PASSED
✔ 11. Task 03 - ABP join procedure [5] PASSED
✔ 11. Task 04 - LoRaWAN device parameters persistence PASSED
✖ 11. Task 05 - GNRC LoRaWAN (Over The Air Activation) [otaa] FAILED
🟡 11. Task 06 - GNRC LoRaWAN (ABP) [abp] SKIPPED

@MrKevinWeiss
Copy link
Contributor

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?

@MrKevinWeiss
Copy link
Contributor

All other automated tests that failed seem to be "experimental" meaning we know they are failing...

@MrKevinWeiss
Copy link
Contributor

The reporting to matrix is also broken but likely a token issue and not critical for this release.

@MrKevinWeiss
Copy link
Contributor

@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.

@MrKevinWeiss
Copy link
Contributor

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 and tests/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 places
    • tests/pkg/libschc flakey
    • tests/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...

@benpicco
Copy link
Contributor Author

benpicco commented Aug 1, 2023

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

@MrKevinWeiss
Copy link
Contributor

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

@MrKevinWeiss
Copy link
Contributor

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.

@benpicco
Copy link
Contributor Author

benpicco commented Aug 7, 2023

Did we ever report the issue to the Zephyr issue tracker?

@MrKevinWeiss
Copy link
Contributor

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.

@benpicco
Copy link
Contributor Author

benpicco commented Aug 7, 2023 •
edited
Loading

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

@MrKevinWeiss
Copy link
Contributor

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?

@benpicco
Copy link
Contributor Author

benpicco commented Aug 7, 2023

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.

@MrKevinWeiss
Copy link
Contributor

I think this one is finished 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@benpicco @riot-ci @MrKevinWeiss