feat(ci): Run esp-idf examples on targets

[peter-marcisovsky]

Description

Running esp-idf usb host and usb device examples with overridden local components on target runners.

Related

• Follow-up for feat(ci): Build idf examples with overriden class driver components #265

Limitations

• NCM Device examples can't be currently run on GH Runners
  • docker container must be executed with --net=host option (same as it is done on GL runners where the NCM device tests are passing) to access host network interface, not possible due to default GH runners config
  • the solution is tested locally and working
• idf examples for IDF 5.4 and older releases are not run, due to complicated CI setup
  • in GL CI, there is a dedicated container target-test-env for this purpose

Changes

Target runners

• usb_device target runners in esp-usb run esp-idf device examples
• usb_host_flash_disk target runners in esp-usb run esp-idf host examples

Conditional workflow run

• the build_and_run_idf_examples.yml workflow run conditionally specified by the PR author
• to save some CI build time, as this test don't have to be build for every PR
• the workflow runs if a PR label BUILD_AND_TEST_IDF_EXAMPLES is present - user can add this label to trigger the run

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

---

Note

Runs esp-idf USB host/device examples on hardware with artifact-based handoff between build and run jobs, and introduces centralized example-selection rules.

• Adds .github/ci/.idf-build-examples-rules.yml to enable/disable usb examples (notably enables host/uvc for IDF_VERSION >= 5.5; disables when SOC_USB_OTG_SUPPORTED != 1, and for NCM also when SOC_WIFI_SUPPORTED != 1).
• Reworks build_and_run_idf_examples.yml to:
  • Gate execution via BUILD_AND_TEST_IDF_EXAMPLES label; build matrix for IDF 5.2–latest; upload build artifacts.
  • Always override esp_tinyusb for device and override host class/usb components as appropriate; create idf_component.yml for usb_host_lib on <6.0.
  • New "run" job on self-hosted runners (esp32s2, esp32p4) for IDF ≥5.5; excludes esp32p4 on some versions; installs deps and executes pytest with markers.
• Minor CI hygiene in build_and_run_test_app_usb.yml: switch to apt-get and add --no-cache-dir to pip installs.

^{Written by Cursor Bugbot for commit 96b07e8. This will update automatically on new commits. Configure here.}

[peter-marcisovsky]

The CI workflow correctly accessed esp32p4 usb_host_flash_disk runners, but there is the error about esp32p4 ECO versions mismatch on the esp-idf Latest :

esptool.util.FatalError: '/opt/esp/idf/examples/peripherals/usb/host/usb_host_lib/build_esp32p4_default/bootloader/bootloader.bin' requires chip revision in range [v3.0 - v3.99] (this chip is revision v1.0). Use the force argument to flash anyway.

Build is for esp32p4 ECO5, the runners are not ECO5.
Disabling the esp32p4 usb_host_flash_disk run for esp-idf latest until the new runners are avaliable.

[peter-marcisovsky]

Converted to draft, as the github runners are failing to run ncm device tests. Will fix this issue in another PR

[peter-marcisovsky]

@tore-espressif @igi540
PR is (again) ready, after solving all the ci setup issues. PTAL

[peter-marcisovsky]

esp-idf device examples backports to use esp_tinyusb v 2.x.x merged in all IDF releases CI passed, ready for merge.

[igi540]

LGTM. I left few nitpicks in the inline comments.

[tore-espressif]

@peter-marcisovsky LGTM, just one comment that could make it a little cleaner

[peter-marcisovsky]

@tore-espressif the --ignore-result-cases implemented as suggested.

FYI I added back the conditional run, which I lost somewhere during rebasing I guess 😕 Just this two lines. And updated the label name to align with your label to run all test apps.

So the conditional run is only based on this label, not on both the label and PR name as I had it before.