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

[TRACKING] cpu/esp*: compile tests for ESP specific modules required #12960

Open
18 of 19 tasks
gschorcht opened this issue Dec 16, 2019 · 3 comments
Open
18 of 19 tasks

[TRACKING] cpu/esp*: compile tests for ESP specific modules required #12960

gschorcht opened this issue Dec 16, 2019 · 3 comments
Assignees
@gschorcht
Labels
Area: cpu Area: CPU/MCU ports Area: tests Area: tests and testing framework Platform: ESP Platform: This PR/issue effects ESP-based platforms Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation

Comments

@gschorcht
Copy link
Contributor

gschorcht commented Dec 16, 2019 •
edited
Loading

Description

To be able to recognize compile errors for ESP specific modules caused by unrelated PRs, a number of compile tests that use these ESP specific modules are required.

  • esp_eth: is the default netdev for esp-32-olimex-evb used by examples/gnrc_networking (ESP32 only)
  • esp_gdb: no test application required, it just enables -Og instead of -Os (ESP32 and ESP8266)
  • esp_gdbstub: (ESP8266 only)
  • esp_hw_counter: used for esp32-wrover-kit when compiled in CI with module periph_timer (ESP32 only)
  • esp_i2c_hw: used for esp32-wrover-kit when compiled in CI with module periph_i2c (ESP32 only)
  • esp_idf_heap: used when esp_now or esp-wifi is used (ESP32 only)
  • esp_jtag: is enabled by default on esp32-wrover-kit (ESP32 only)
  • esp_log_colored: tested by tests/log_color (ESP32 and ESP8266)
  • esp_log_startup: used for esp32-wrover-kit and esp8266-olimex-mod when compiled in CI (ESP32 and ESP8266)
  • esp_log_tagged: used for esp32-wrover-kit and esp8266-olimex-mod when compiled in CI (ESP32 and ESP8266)
  • esp_now: is the default netdev for all ESP boards used by examples/gnrc_networking (ESP32 and ESP8266)
  • esp_qemu: used for esp32-wrover-kit and esp8266-olimex-mod when compiled in CI (ESP32 and ESP8266)
  • esp_rtc_timer_32k: used for esp32-wrover-kit in tests/periph_rtc (ESP32 only)
  • esp_spi_ram: used for esp32-wrover-kit when compiled in CI (ESP32 only)
  • esp_spiffs: used by tests/spiffs and tests/littlefs (ESP32 and ESP8266)
  • esp_sw_timer: used for esp8266-olimex-mod when compiled in CI with module periph_timer (ESP8266 only)
  • esp_wifi: is used for lwip as default netdev if no other netdev is enabled (ESP32 and ESP8266)
  • esp_wifi_ap: used for esp32-wrover-kit and esp8266-olimex-mod when compiled in CI with module gnrc_netif_single (ESP32 and ESP8266)
  • esp_wifi_enterprise: used for esp32-wrover-kit when compiled in CI with module netdev_default (ESP32 only)
@gschorcht gschorcht self-assigned this Dec 16, 2019
@gschorcht gschorcht added Area: cpu Area: CPU/MCU ports Area: tests Area: tests and testing framework Platform: ESP Platform: This PR/issue effects ESP-based platforms Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation labels Dec 16, 2019
@gschorcht gschorcht mentioned this issue Dec 17, 2019
Closed
@stale
Copy link

stale bot commented Jul 29, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Jul 29, 2020
@gschorcht gschorcht removed the State: stale State: The issue / PR has no activity for >185 days label Jul 29, 2020
@stale
Copy link

stale bot commented Feb 9, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Feb 9, 2021
@gschorcht
Copy link
Contributor Author

gschorcht commented Feb 10, 2021 •
edited
Loading

It's still an open issue.

@gschorcht gschorcht removed the State: stale State: The issue / PR has no activity for >185 days label Feb 10, 2021
@MrKevinWeiss MrKevinWeiss added this to the Release 2021.07 milestone Jun 22, 2021
@MrKevinWeiss MrKevinWeiss removed this from the Release 2021.07 milestone Jul 15, 2021
This was referenced Dec 1, 2021
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gschorcht gschorcht

Labels
Area: cpu Area: CPU/MCU ports Area: tests Area: tests and testing framework Platform: ESP Platform: This PR/issue effects ESP-based platforms Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MrKevinWeiss @gschorcht