ci(tinyusb): Run tinyusb tests in CI for esp32p4 #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This MR enables
esp_tinyusb
tests in CI on a newusb_device
esp32p4
runner.The new runner
BrnoRPIG009
was updated with a script introduced in #75, allowing us to access USB devices from running docker container.In esp_tinyusb, there are 3 groups of tests:
pytest_cdc.py
- Test is run in CIpytest_usb_device.py
- Test not run in CI, missing teradown function in tinyusb (also bvalid signal test not tested on esp32p4)pytest_vendor.py
- Test not run in CI due to Docker container problems accessing a vendor specific deviceRelated
Follow-up
Testing
To pass current CI tests
Checklist
Before submitting a Pull Request, please ensure the following: