Test v0.6.6
I maintainer di solito rispondono entro 2 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 20/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Ambito
- embedded-iot, testing
Direzione di ricerca
Start with the release binaries linked in the issue and run the listed checks on the available hardware and platforms, recording hardware, SDK and compiler versions, build type, logs, and results. Add results to the checklist and report any proposed component checks or uptime runs; completion means the release checks have documented outcomes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Let's run a number of manual tests and additional checks in order to make sure v0.6.6 will be the best release ever.
Test binaries can be found here: https://github.com/bettio/avm_tag_ci/releases/tag/v0.6.6202506192
Please, let's use real hardware.
Please comment to this issue reporting additional information such as esp-idf version/sdk version/compiler version or any boot log. Any additional information in addition to the short test output is appreciated. Please, also mention if any prebuilt image is used or a custom build.
Let's also propose additional components we would like to test,
General
- Can be compiled with C++ libraries
External Components
- AtomGL component works
- ESP32 audio pipe component works
- ESP32 cam component
- DHT component (atomvm_dht)
- atomvm_lib/BME280
- atomvm_lib/BH1750
- atomvm_lib/SHT3X
- atomvm_m5
- atomvm_mqtt_client
- atomvm_neopixel
ESP32
Devices:
- boots on ESP32
- boots on ESP32-S2
- boots on ESP32-S3
- boots on ESP32-C2
- boots on ESP32-C3
- boots on ESP32-C6
- boots on ESP32-H2
Network features:
- Connects to wifi AP
- Works as wifi AP
- Date and time is updated using time server
- ssl works
- gen_tcp works
- gen_udp works
- socket works
Peripherals:
- ADC read
- ledc
- GPIO read
- GPIO write
- GPIO interrupt
- i2c read
- i2c write
- SPI read
- SPI write
- UART read
- UART write
Misc:
- SD with SPI can be mounted
- SD with MMC can be mounted
- SPI flash partition can be mounted
- RTC memory works
- NVS works
- deep sleep works and RTC data is retained
- posix file support works
- Generated artifacts do not contain truncated or invalid data (e.g. libraries bigger than their partition, etc...)
Usage scenarios:
- Developer mode with ALISP works
- Developer web configuration page works
- http client works
- https client works
- A complex Elixir application making use of protocols such as Enum works
RP2040
- Boots on regular RP2040
- Boots on wifi enabled RP2040
- Output to console
- Connects to wifi AP
- sockets works
- ssl works
Peripherals:
- GPIO read
- GPIO write
emscripten
- Supervisor bubbles tests works
- elixir REPL PoC works
- erlang REPL PoC works
generic_unix (linux)
- gen_tcp works
- gen_udp works
- socket works
- ssl works
- posix file support works
Usage scenarios:
- Port drivers plugins are working
- http client works
- https client works
- A complex Elixir application making use of protocols such as Enum works
generic_unix (macOS)
- gen_tcp works
- gen_udp works
- socket works
- ssl works
- posix file support works
- A complex Elixir application making use of protocols such as Enum works
Usage scenarios:
- Port drivers plugins are working
- http client works
- https client works
- A complex Elixir application making use of protocols such as Enum works
STM32
- Boots
- Output to console
- GPIO write
"Uptime Loop Test"
The following are proposed tests to find if we have any memory leak or any other issue that prevents a system to run for a long time without any crash.
Let's keep track of uptime (with no crashes or reboots) when running some application performing tasks in loop.
E.g. "uptime with a GPS parsing library that handles GPS messages every 0.5 second", "uptime when refreshing display with a counter every second", "uptime when running benchmarks in loop" etc...
- Lingua principale
- Erlang
- Stelle
- 2.3k
- Fork
- 171
- Merge medio
- 5g 11h
- PR unite (30g)
- 19
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di atomvm/AtomVM
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 2 giorni
-
unicode:characters_to_list/binary return an uninitialized term for a non-chardata argumentForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
atomvm/AtomVM#2435 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
atomvm/AtomVM#2429 · 1 reazione ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di atomvm/AtomVM
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Turn on if screen is touchedAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
FujiNetWIFI/fujinet-firmware#2341 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
zephyrproject-rtos/zephyr#125203 ·
I maintainer di solito rispondono entro 2 giorni