-
Notifications
You must be signed in to change notification settings - Fork 3
Default arduino_ci configuration may test platforms/architectures that, according to library.properties, are unsupported #11
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.
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
Comments
Hi @feilipu! Sorry for my delayed reply, I got the email but thought that you had opened this against the project that underlies this github action (https://github.com/Arduino-CI/arduino_ci/issues) I will move these issues there. The short answer(s) here are that As far as the espressif board problems, I that discussion is spread over a few projects and I'll link them. I can respond more fully in a bit but I wanted to acknowledge that I saw this. |
Thanks Ian. I need this set to be included at least as headers. #include <avr/io.h>
#include <avr/interrupt.h>
#include <avr/sleep.h>
#include <avr/wdt.h> |
Looking again at the build log, it appears that the error (printed below) is coming from the "backend", which is the
If this builds in the Arduino IDE but not with |
I see the library specifies that it is only for the AVR archtecture. So I think the problem here is that Arduino CI has not been configured to only compile for AVR. |
By this, I mean the problem is the lack of See this section of the documentation: |
Aah OK -- so the issue is that (presumably) this library was only ever meant for AVR but Arduino CI's default behavior of also testing @feilipu as a new user, can you discuss some ways that the software might have reported that to you in a more actionable way? For example, is it surprising to you that your library doesn't work on non-AVR architecture? Or is the surprise that |
@ianfixes I've simply followed the instructions as noted on the Arduino Developers' Google Group to try to get CI working. The action on failure was pretty clear; just raise an issue, as I've done. So nothing to improve there. Perhaps if this is not the right place to raise the issue, then correct the links to enable others to do better. The library itself is specifically and only for AVR ATmega architecture, and it is reported as such in its properties file. I wasn't aware that additional files, such as a |
Thank you for taking the time to try it out, and even more so for taking the time to describe your experience here.
Aah! That's something I should be reading and reacting to. Opened Arduino-CI/arduino_ci#246
This is a valuable signal to me that I don't have the right documentation in the right places. I'm very curious what documentation of mine that you encountered while setting up & using Opened #12
This is straightforward. But if you'll indulge me, I'm wondering if you could attempt to find it in the docs and let me know if it's not easy to find. You're right that it's entirely possible for an example within a library to include dependencies beyond the library itself, and so I support that use case directly. |
If you'd like to try this in an experimental branch, including the action as |
I've revised the workflow file, and there is a new issue with the ruby gems solution. Not sure if this is transient, or something more important.
|
Looks like the failure is here https://github.com/Arduino-CI/arduino_ci/blob/master/exe/arduino_ci.rb#L483 I'm somewhat confused, because we did a lot of testing on this branch. But I'll have to dig into it tomorrow. Can you open a new issue with this info? This bug is different than the one you reported initially. In the meantime, I have a development branch that you can try by changing steps:
- uses: actions/checkout@v2
- - uses: Arduino-CI/[email protected] # v0.1.2 or the latest version
+ - uses: Arduino-CI/action@latest # development branch, in flux Any changes I try out would hit that branch first. |
My library uses standard avr-libc headers provided by the Arduino IDE normally, and the lack of these headers is breaking the CI workflow.
How can I add appropriate scripting to ensure they're provided?
Also, independently, I need to prevent the workflow from attempting to compile against the ESP8266, as it is AVR only library.
How can that be done?
The text was updated successfully, but these errors were encountered: