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.

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 2022.04 - RC6 #247

Closed
63 of 88 tasks
OlegHahm opened this issue Apr 26, 2022 · 28 comments
Closed
63 of 88 tasks

Release 2022.04 - RC6 #247

OlegHahm opened this issue Apr 26, 2022 · 28 comments

Comments

@OlegHahm
Copy link
Member

OlegHahm commented Apr 26, 2022

This issue lists the status of all tests for the Release Candidate 6 of the 2022.04 release.

Specs tested:

@riot-ci
Copy link

riot-ci commented Apr 26, 2022

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-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-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-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-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-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) SKIPPED
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 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 SKIPPED
🟡 04. Task 12 (Experimental) - ICMPv6 multicast echo with iotlab-m3/nrf802154 SKIPPED
🟡 04. Task 13 (Experimental) - ICMPv6 link-local echo with iotlab-m3/nrf802154 SKIPPED
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 03 - ABP join procedure FAILED
11. Task 04 - LoRaWAN device parameters persistence PASSED
11. Task 05 - GNRC LoRaWAN (Over The Air Activation) [otaa] PASSED
🟡 11. Task 06 - GNRC LoRaWAN (ABP) [abp] SKIPPED

@OlegHahm
Copy link
Member Author

@MrKevinWeiss, @benpicco, @fjmolinas, @bergzand, could you help with the interop tests?
@kaspar030, could you run the build tests on murdock again?

@MrKevinWeiss
Copy link
Contributor

Sure, I can give it a try tomorrow morning. I thought some were already done by @jia200x. Did you want all (possible) one rerun?

@OlegHahm
Copy link
Member Author

I'm not aware of any previous runs.

@MrKevinWeiss
Copy link
Contributor

UDP exchange between iotlab-m3 and Contiki (:heavy_check_mark: PASS)

riot

> udp send fe80::0212:4b00:0422:9db8 3000 1
2022-04-27 11:40:36,234 # udp send fe80::0212:4b00:0422:9db8 3000 1
2022-04-27 11:40:36,236 # Success: send 1 byte to [fe80::0212:4b00:0422:9db8]:3000
> udp send fe80::0212:4b00:0422:9db8 3000 3
2022-04-27 11:40:39,161 # udp send fe80::0212:4b00:0422:9db8 3000 3
2022-04-27 11:40:39,163 # Success: send 3 byte to [fe80::0212:4b00:0422:9db8]:3000

contiki

2022-04-27 11:38:44,221 # Contiki-3.x-3345-g32b5b17f6
2022-04-27 11:38:44,223 # TI SmartRF06 + cc2538EM
2022-04-27 11:38:44,237 # CC2538: ID: 0xb965, rev.: PG2.0, Flash: 512 KiB, SRAM: 32 KiB, AES/SHA: 1, ECC/RSA: 1
2022-04-27 11:38:44,239 # System clock: 16000000 Hz
2022-04-27 11:38:44,240 # I/O clock: 16000000 Hz
2022-04-27 11:38:44,241 # Reset cause: External reset
2022-04-27 11:38:44,241 #  Net: sicslowpan
2022-04-27 11:38:44,242 #  MAC: CSMA
2022-04-27 11:38:44,243 #  RDC: nullrdc
2022-04-27 11:38:44,253 # Rime configured with address 00:12:4b:00:04:22:9d:b8
2022-04-27 11:38:44,254 # Starting UDP echo server
2022-04-27 11:38:44,255 # Listen port: 3000, TTL=64
2022-04-27 11:40:30,567 # 1 bytes from [fe80::a884:9937:4f86:7b4e]:3000
2022-04-27 11:40:36,248 # 1 bytes from [fe80::a884:9937:4f86:7b4e]:3000
2022-04-27 11:40:39,175 # 3 bytes from [fe80::a884:9937:4f86:7b4e]:3000

@MrKevinWeiss
Copy link
Contributor

Note that the Zephyr node crashes after the echo (we assume it is not riots fault), tested on the old version of zephyr and the new version.

UDP exchange between iotlab-m3 and Zephyr (Mostly PASS)
2022-04-27 13:36:02,116 # ifconfig
2022-04-27 13:36:02,119 # Iface  6  HWaddr: 7B:4E  Channel: 26  Page: 0  NID: 0xabcd  PHY: O-QPSK 
2022-04-27 13:36:02,119 #           
2022-04-27 13:36:02,121 #           Long HWaddr: AA:84:99:37:4F:86:7B:4E 
2022-04-27 13:36:02,124 #            TX-Power: 0dBm  State: IDLE  max. Retrans.: 3  CSMA Retries: 4 
2022-04-27 13:36:02,126 #           AUTOACK  ACK_REQ  CSMA  L2-PDU:102  MTU:1280  HL:64  RTR  
2022-04-27 13:36:02,127 #           6LO  IPHC  
2022-04-27 13:36:02,128 #           Source address length: 8
2022-04-27 13:36:02,130 #           Link type: wireless
2022-04-27 13:36:02,132 #           inet6 addr: fe80::a884:9937:4f86:7b4e  scope: link  VAL
2022-04-27 13:36:02,133 #           inet6 group: ff02::2
2022-04-27 13:36:02,134 #           inet6 group: ff02::1
2022-04-27 13:36:02,136 #           inet6 group: ff02::1:ff86:7b4e
2022-04-27 13:36:02,137 #           inet6 group: ff02::1a
2022-04-27 13:36:02,137 #           
2022-04-27 13:36:02,139 #           Statistics for Layer 2
2022-04-27 13:36:02,140 #             RX packets 114  bytes 7311
2022-04-27 13:36:02,142 #             TX packets 201 (Multicast: 26)  bytes 8587
2022-04-27 13:36:02,144 #             TX succeeded 82 errors 119
2022-04-27 13:36:02,144 #           Statistics for IPv6
2022-04-27 13:36:02,145 #             RX packets 114  bytes 8622
2022-04-27 13:36:02,146 #             TX packets 201 (Multicast: 26)  bytes 12255
2022-04-27 13:36:02,147 #             TX succeeded 201 errors 0
2022-04-27 13:36:02,148 # 
 udp send fe80::445b:100:d425:9c3b 4242 "RIOT Testing!"
2022-04-27 13:36:59,840 # udp send fe80::445b:100:d425:9c3b 4242 "RIOT Testing!"
2022-04-27 13:36:59,843 # Success: sent 13 byte(s) to [fe80::445b:100:d425:9c3b]:4242
 udp send fe80::808b:100:1056:9c3b 4242 "RIOT Testing!"
2022-04-27 13:38:25,978 # udp send fe80::808b:100:1056:9c3b 4242 "RIOT Testing!"
2022-04-27 13:38:25,994 # Success: sent 13 byte(s) to [fe80::808b:100:1056:9c3b]:4242
> 2022-04-27 13:38:26,004 # PKTDUMP: data received:
2022-04-27 13:38:26,006 # ~~ SNIP  0 - size:  13 byte, type: NETTYPE_UNDEF (0)
2022-04-27 13:38:26,009 # 00000000  52  49  4F  54  20  54  65  73  74  69  6E  67  21
2022-04-27 13:38:26,011 # ~~ SNIP  1 - size:   8 byte, type: NETTYPE_UDP (4)
2022-04-27 13:38:26,012 #    src-port:  4242  dst-port:  4242
2022-04-27 13:38:26,013 #    length: 21  cksum: 0x7bba
2022-04-27 13:38:26,015 # ~~ SNIP  2 - size:  40 byte, type: NETTYPE_IPV6 (2)
2022-04-27 13:38:26,017 # traffic class: 0x00 (ECN: 0x0, DSCP: 0x00)
2022-04-27 13:38:26,018 # flow label: 0x00000
2022-04-27 13:38:26,019 # length: 21  next header: 17  hop limit: 64
2022-04-27 13:38:26,021 # source address: fe80::808b:100:1056:9c3b
2022-04-27 13:38:26,023 # destination address: fe80::a884:9937:4f86:7b4e
2022-04-27 13:38:26,025 # ~~ SNIP  3 - size:  24 byte, type: NETTYPE_NETIF (-1)
2022-04-27 13:38:26,026 # if_pid: 6  rssi: -52  lqi: 255
2022-04-27 13:38:26,026 # flags: 0x0
2022-04-27 13:38:26,027 # src_l2addr: 82:8B:01:00:10:56:9C:3B
2022-04-27 13:38:26,028 # dst_l2addr: AA:84:99:37:4F:86:7B:4E
2022-04-27 13:38:26,029 # ~~ PKT    -  4 snips, total size:  85 byte

@kaspar030
Copy link
Contributor

kaspar030 commented Apr 27, 2022

Note that the Zephyr node crashes after the echo (we assume it is not riots fault), tested on the old version of zephyr and the new version.

Interop test passed. Other implementation crashed. ;)

@benpicco
Copy link
Contributor

We should probably open an issue for that

@aabadie
Copy link
Contributor

aabadie commented Apr 27, 2022

A bit off-topic but the iot-lab team started to port Zephyr to the iotlab-m3. This WIP work is in an iot-lab fork. Basic stuff are working but not the radio... If one day it works, it will be possible to run the interop between 2 iotlab-m3 (1 running RIOT, the other running Zephyr) 😃

@MrKevinWeiss
Copy link
Contributor

Just to be clear, also Zephyr board will randomly crash after some time (after about 10 seconds). previous 1 2 3 runs seemed to have varied results and I remember these issues always being present.

@leandrolanzieri had to play around with the buffer sizes to make the firmware fit which may have contributed to it (or not).

Either way I would say "exists in previous releases" or something to that effect.

@jia200x
Copy link
Member

jia200x commented Apr 27, 2022

All {RIOT, RPI}-border router test passed.
Only the ESP tasks are missing. @benpicco you ran some of these tests during last releases, could you give it a try?

@jia200x
Copy link
Member

jia200x commented Apr 27, 2022

@OlegHahm
Copy link
Member Author

@OlegHahm
Copy link
Member Author

I ran 62 random tests on samr21-xpro and got 62 test.success files.

@OlegHahm
Copy link
Member Author

Running the unit-tests on native again with
BUILD_IN_DOCKER=1 RIOT_CI_BUILD=1 dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . native
I got

ERROR:native:Tests failed: 13
Failures during compilation:
- [tests/gnrc_sixlowpan_frag_minfwd](tests/gnrc_sixlowpan_frag_minfwd/compilation.failed)
- [tests/gnrc_sixlowpan_frag_sfr](tests/gnrc_sixlowpan_frag_sfr/compilation.failed)
- [tests/kconfig](tests/kconfig/compilation.failed)
- [tests/kconfig_features](tests/kconfig_features/compilation.failed)

Failures during test:
- [examples/micropython](examples/micropython/test.failed)
- [tests/congure_test](tests/congure_test/test.failed)
- [tests/gnrc_netif_ieee802154](tests/gnrc_netif_ieee802154/test.failed)
- [tests/lwip](tests/lwip/test.failed)
- [tests/netstats_l2](tests/netstats_l2/test.failed)
- [tests/pkg_edhoc_c](tests/pkg_edhoc_c/test.failed)
- [tests/thread_float](tests/thread_float/test.failed)
- [tests/turo](tests/turo/test.failed)
- [tests/ztimer_periodic](tests/ztimer_periodic/test.failed)

I thought that RIOT_CI_BUILD=1 should prevent the ztimer_periodic test from being executed!? @kaspar030? What about the other failures? Any idea?

@kaspar030
Copy link
Contributor

I thought that RIOT_CI_BUILD=1 should prevent the ztimer_periodic test from being executed!?

RIOT_CI_BUILD mostly sets options so builds stay reproducible (e.g., not use the git commit hash in RIOT's hello message), and quiets down the build.

Murdock honors TEST_ON_CI_BLACKLIST, I don't think compile_and_test_for_board.py does.

What about the other failures? Any idea?

The compile failures, I don't know.

  • examples/micropython, tests/thread_float probably fail because native is not float safe (both blacklisted)
  • tests/ztimer_periodic is timing sensitive (blacklisted)
  • tests/lwip, tests/netstats_l2, tests/pkg_edhoc_c are blacklisted
❯ for i in examples/micropython tests/congure_test tests/gnrc_netif_ieee802154 tests/lwip tests/netstats_l2 tests/pkg_edhoc_c tests/thread_float tests/turo tests/ztimer_periodic ; do grep -H BLACKLIST $i/Makefile; done | grep -E '(all|native)'
tests/lwip/Makefile:TEST_ON_CI_BLACKLIST += all
tests/netstats_l2/Makefile:TEST_ON_CI_BLACKLIST += native
tests/pkg_edhoc_c/Makefile:TEST_ON_CI_BLACKLIST += native
tests/thread_float/Makefile:TEST_ON_CI_BLACKLIST += native
tests/ztimer_periodic/Makefile:TEST_ON_CI_BLACKLIST += native


@OlegHahm
Copy link
Member Author

Interestingly the compile errors only occur when I build them with BUILD_IN_DOCKER. The reason in all four cases looks similar:

Launching build container using image "riot/riotbuild:latest".
docker run --rm --tty --user $(id -u) -v '/usr/share/zoneinfo/Europe/Berlin:/etc/localtime:ro' -v '/home/oleg/git/RIOT:/data/riotbuild/riotbase:delegated' -v '/home/oleg/.cargo/registry:/data/riotbuild/.cargo/registry:delegated' -v '/home/oleg/.cargo/git:/data/riotbuild/.cargo/git:delegated' -e 'RIOTBASE=/data/riotbuild/riotbase' -e 'CCACHE_BASEDIR=/data/riotbuild/riotbase' -e 'BUILD_DIR=/data/riotbuild/riotbase/build' -e 'RIOTPROJECT=/data/riotbuild/riotbase' -e 'RIOTCPU=/data/riotbuild/riotbase/cpu' -e 'RIOTBOARD=/data/riotbuild/riotbase/boards' -e 'RIOTMAKE=/data/riotbuild/riotbase/makefiles'       -e 'DISABLE_MODULE=' -e 'DEFAULT_MODULE=test_utils_interactive_sync test_utils_print_stack_usage' -e 'FEATURES_REQUIRED=' -e 'FEATURES_BLACKLIST=' -e 'FEATURES_OPTIONAL=' -e 'USEMODULE=external_module_1 external_module_2' -e 'USEPKG=external_pkg_1 external_pkg_2' -e 'KCONFIG_ADD_CONFIG='  -w '/data/riotbuild/riotbase/tests/kconfig/' 'riot/riotbuild:latest' make  'EXTERNAL_MODULE_DIRS=/data/riotbuild/riotbase/tests/kconfig/external_modules'   
Building application "tests_kconfig" for "native" with MCU "native".

"make" -C /data/riotbuild/riotbase/tests/kconfig/external_pkgs/external_pkg_1/ 
"make" -C /data/riotbuild/riotbase/tests/kconfig/external_pkgs/external_pkg_2/ 
/data/riotbuild/riotbase/dist/tools/fixdep/fixdep: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /data/riotbuild/riotbase/dist/tools/fixdep/fixdep)
/data/riotbuild/riotbase/dist/tools/fixdep/fixdep: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /data/riotbuild/riotbase/dist/tools/fixdep/fixdep)
make[1]: *** [/data/riotbuild/riotbase/Makefile.base:147: /data/riotbuild/riotbase/tests/kconfig/bin/native/application_tests_kconfig/main.o] Error 1
make: *** [/data/riotbuild/riotbase/Makefile.include:737: application_tests_kconfig.module] Error 2
make: *** [/home/oleg/git/RIOT/makefiles/docker.inc.mk:350: ..in-docker-container] Error 2

The tests build just fine when built without docker.

@OlegHahm
Copy link
Member Author

Okay, two other tests failed because python-rapidjson was not installed on my machine.

So, basically all tests that should succeed now, except for tests/gnrc_netif_ieee802154 which fails with:

 % make test                                                                                                                                                   [22:31:13][0]
r
/home/oleg/git/RIOT/tests/gnrc_netif_ieee802154/bin/native/tests_gnrc_netif_ieee802154.elf -z "0.0.0.0:17755,localhost:17754" /dev/ttyACM0 
RIOT native interrupts/signals initialized.
RIOT native board initialized.
RIOT native hardware initialization complete.

/home/oleg/git/RIOT/tests/gnrc_netif_ieee802154/bin/native/tests_gnrc_netif_ieee802154.elf: ZEP: Unable to connect socket: Bad file descriptor

@miri64, do you have an idea here?

@kaspar030
Copy link
Contributor

So, basically all tests that should succeed now, except for tests/gnrc_netif_ieee802154 which fails with:

The python tests script uses "scapy", maybe that needs to be installed?

@benpicco
Copy link
Contributor

benpicco commented Apr 27, 2022

Task #12 - ICMPv6 echo between Border Router with WiFi uplink to named Internet host - broken

2022-04-27 23:20:17,518 # rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
2022-04-27 23:20:17,520 # configsip: 0, SPIWP:0xee
2022-04-27 23:20:17,526 # clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
2022-04-27 23:20:17,528 # mode:DOUT, clock div:2
2022-04-27 23:20:17,530 # load:0x3fff0018,len:4
2022-04-27 23:20:17,533 # load:0x3fff001c,len:4004
2022-04-27 23:20:17,535 # load:0x40078000,len:7304
2022-04-27 23:20:17,537 # load:0x40080000,len:7224
2022-04-27 23:20:17,539 # entry 0x40080350
2022-04-27 23:20:17,545 # W (29) boot: PRO CPU has been reset by WDT.
2022-04-27 23:20:17,549 # W (29) boot: WDT reset info: PRO CPU PC=0x400803c3
2022-04-27 23:20:17,554 # W (29) boot: WDT reset info: APP CPU PC=0x2f3378fb
2022-04-27 23:20:17,785 # 
2022-04-27 23:20:19,525 # NETOPT_RX_END_IRQ not implemented by driver
2022-04-27 23:20:19,790 # Serial port disconnected, waiting to get reconnected...
2022-04-27 23:20:20,792 # Try to reconnect to /dev/ttyUSB1 again...
2022-04-27 23:20:20,799 # Reconnected to serial port /dev/ttyUSB1
2022-04-27 23:20:25,524 # ets Jun  8 2016 00:22:57
2022-04-27 23:20:25,525 # 
2022-04-27 23:20:25,530 # rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
2022-04-27 23:20:25,532 # configsip: 0, SPIWP:0xee
2022-04-27 23:20:25,538 # clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
2022-04-27 23:20:25,540 # mode:DOUT, clock div:2
2022-04-27 23:20:25,542 # load:0x3fff0018,len:4
2022-04-27 23:20:25,544 # load:0x3fff001c,len:4004
2022-04-27 23:20:25,547 # load:0x40078000,len:7304
2022-04-27 23:20:25,549 # load:0x40080000,len:7224
2022-04-27 23:20:25,551 # entry 0x40080350
2022-04-27 23:20:25,557 # W (29) boot: PRO CPU has been reset by WDT.
2022-04-27 23:20:25,561 # W (29) boot: WDT reset info: PRO CPU PC=0x4008e5ac
2022-04-27 23:20:25,566 # W (29) boot: WDT reset info: APP CPU PC=0x2f3378fb
2022-04-27 23:20:25,796 # 
2022-04-27 23:20:27,537 # NETOPT_RX_END_IRQ not implemented by driver

board is stuck in a boot loop

same on 2022.01-branch

2022-04-27 23:18:34,298 # rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
2022-04-27 23:18:34,300 # configsip: 0, SPIWP:0xee
2022-04-27 23:18:34,307 # clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
2022-04-27 23:18:34,309 # mode:DOUT, clock div:2
2022-04-27 23:18:34,311 # load:0x3fff0018,len:4
2022-04-27 23:18:34,313 # load:0x3fff001c,len:4004
2022-04-27 23:18:34,315 # load:0x40078000,len:7304
2022-04-27 23:18:34,317 # load:0x40080000,len:7224
2022-04-27 23:18:34,319 # entry 0x40080350
2022-04-27 23:18:34,562 # 
2022-04-27 23:18:36,302 # NETOPT_RX_END_IRQ not implemented by driver
2022-04-27 23:18:36,466 # phy_version: 3910, c0c45a3, May 21 2018, 18:07:06, 0, 2
2022-04-27 23:18:36,475 # NETOPT_RX_END_IRQ not implemented by driver
2022-04-27 23:18:36,479 # DHCPv6: Selecting interface 9 as upstream
2022-04-27 23:18:36,482 # DHCPv6: Selecting interface 9 as upstream
2022-04-27 23:18:36,488 # main(): This is RIOT! (Version: 2022.04-devel-5-g6a8ded-2022.01-branch)
2022-04-27 23:18:36,492 # RIOT border router example application
2022-04-27 23:18:36,494 # All up, running the shell now

2022-04-27 23:18:48,203 # ping riot-os.org
2022-04-27 23:18:48,239 # 12 bytes from 2001:67c:254:b0b0::1: icmp_seq=0 ttl=60 time=20.864 ms
2022-04-27 23:18:49,239 # 12 bytes from 2001:67c:254:b0b0::1: icmp_seq=1 ttl=60 time=21.034 ms
2022-04-27 23:18:50,239 # 12 bytes from 2001:67c:254:b0b0::1: icmp_seq=2 ttl=60 time=20.998 ms
2022-04-27 23:18:50,239 # 
2022-04-27 23:18:50,242 # --- riot-os.org PING statistics ---
2022-04-27 23:18:50,247 # 3 packets transmitted, 3 packets received, 0% packet loss
2022-04-27 23:18:50,251 # round-trip min/avg/max = 20.864/20.965/21.034 ms

This is with esp32-wroom-32 and xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a5) 5.2.0, same result with xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2-patch3) 8.4.0

@jia200x
Copy link
Member

jia200x commented Apr 27, 2022

@jia200x, do you know what's up with https://github.com/RIOT-OS/Release-Specs/blob/faafe7bcbaf13751b9b07cf5490a7bead13faa27/11-lorawan/README.md#task-03---abp-join-procedure? It failed. Or is it one of the flaky tests, @fjmolinas mentioned?

I ran the semtech lorawan ABP test manually and passed

@OlegHahm
Copy link
Member Author

So, basically all tests that should succeed now, except for tests/gnrc_netif_ieee802154 which fails with:

The python tests script uses "scapy", maybe that needs to be installed?

Hm, scapy was installed already. Does the test work on your machine?

@kaspar030
Copy link
Contributor

Hm, scapy was installed already. Does the test work on your machine?

Yes, tests/gnrc_netif_ieee802154 on native passes here!

@OlegHahm
Copy link
Member Author

So, networking on esp32 is apparently broken!? I tend to call this a blocker for the release.

@OlegHahm
Copy link
Member Author

Hm, scapy was installed already. Does the test work on your machine?

Yes, tests/gnrc_netif_ieee802154 on native passes here!

Good enough for me. :)

@benpicco
Copy link
Contributor

benpicco commented Apr 27, 2022

Found the issue on esp32:

08196603030b735dff4d1569b850ea720d6d5c38 is the first bad commit
commit 08196603030b735dff4d1569b850ea720d6d5c38
Author: @fjmolinas
Date: Wed Mar 2 10:00:00 2022 +0100

sys/syscalls: add libc_gettimeofday

Conditionally implement gettimeofday() if module is included, this
avoids including ztimer64 even when not needed

cpu/native/Kconfig | 1 -
cpu/native/Makefile.dep | 9 ++++++---
cpu/native/syscalls.c | 5 +++--
makefiles/pseudomodules.inc.mk | 4 ++++
pkg/lua/Makefile.dep | 8 ++++++++
pkg/tinydtls/Makefile.dep | 8 ++++++++
pkg/wolfssl/Makefile.dep | 8 ++++++++
sys/Kconfig | 8 +++++++-
sys/Kconfig.newlib | 9 ++++++++-
sys/Makefile.dep | 9 ++++++---
sys/newlib_syscalls_default/syscalls.c | 14 +++-----------
tests/cpp11_mutex/Makefile | 1 +
12 files changed, 62 insertions(+), 22 deletions(-)

With that commit reverted:

2022-04-27 23:42:57,362 # NETOPT_RX_END_IRQ not implemented by driver
2022-04-27 23:42:57,527 # phy_version: 3910, c0c45a3, May 21 2018, 18:07:06, 0, 2
2022-04-27 23:42:57,537 # NETOPT_RX_END_IRQ not implemented by driver
2022-04-27 23:42:57,540 # DHCPv6: Selecting interface 9 as upstream
2022-04-27 23:42:57,544 # DHCPv6: Selecting interface 9 as upstream
2022-04-27 23:42:57,549 # main(): This is RIOT! (Version: 2022.07-devel-256-g9538b8)
2022-04-27 23:42:57,552 # RIOT border router example application
2022-04-27 23:42:57,555 # All up, running the shell now

2022-04-27 23:43:06,700 # > ping riot-os.org
2022-04-27 23:43:07,735 # 12 bytes from 2001:67c:254:b0b0::1: icmp_seq=1 ttl=60 time=21.459 ms
2022-04-27 23:43:08,744 # 12 bytes from 2001:67c:254:b0b0::1: icmp_seq=2 ttl=60 time=31.146 ms
2022-04-27 23:43:09,707 # 
2022-04-27 23:43:09,710 # --- riot-os.org PING statistics ---
2022-04-27 23:43:09,715 # 3 packets transmitted, 2 packets received, 33% packet loss
2022-04-27 23:43:09,720 # round-trip min/avg/max = 21.459/26.302/31.146 ms

@miri64
Copy link
Member

miri64 commented Apr 28, 2022

@miri64, do you have an idea here?

Maybe something went wrong in the socket initialization? But not sure. Happy that it seem to have resolved itself :D

@OlegHahm
Copy link
Member Author

Closing in favor of #248

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants