Issue with Arduino tests
See original GitHub issueRecently Arduino tests started failing with:
Error during build: Platform 'esp32:esp32' not found: platform not installed
Try running `arduino-cli.exe core install esp32:esp32`
It could be specific to some machines.
These tests are disabled here: https://github.com/dotnet/iot/pull/2051
Issue Analytics
- State:
- Created 6 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Arduino Board Testing - Troubleshooting
Hi everybody! I don't see if there is a special topic about testing of Arduino boards. So I've made a simple testing board...
Read more >Unit testing considerations and examples - Project Guidance
Hi, I am beginning to work with the unit testing functionality offered by platformIO and Arduino. I am trying to build my intuition...
Read more >Arduino failing loopback test despite working perfectly ...
I have no problems loading sketches and using the serial port. I tried the loopback test because of the OP and was surprised...
Read more >unit testing and programming - Troubleshooting
Testing on the Arduino must therefore not focus only on the software component, as you then loose focus on the whole. Efficient testing...
Read more >Issues · arduino/Tests
Issues list. ATS in not compatible with modern Arduino 1.8.1 IDE (got error about 'prog_char'). #3 opened on Mar 20, 2017 by N0rbert....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
tests are one thing, but I think I agree with @krwq on disabling Arduino specific build. We have talked about this several times during triage, but essentially the purpose of CI is to ensure and protect against build breaks from the incoming code. Given that the Arduino binding (and other code that might impact it) are very rarely touched, having this leg as part of the build is not really giving us much benefit. In other words, I don’t think this build has ever failed due to a legitimate break in the Arduino binding, except for PRs that were actually touching it which was mostly just work done by @pgrawehr. In the past we had agreed we would move this pipeline to a separate leg that can be invoked on-demand, so I see the change @krwq made on #2051 as part of that process, we just now need to create a new yml and move this code there. After that we can just create a new pipeline that runs on demand.
[Triage] Closing as disabled because they were running for too long and they are anyway run locally when touching the library.