-
Notifications
You must be signed in to change notification settings - Fork 211
Remove unnecessary config values from CI setup #96
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
Conversation
I was going to wait to see whether the tests passed 😉 |
The remaining error looks like a problem with the platform definition.
I'm not familiar enough with that architecture to say what the fix should be. |
Just one failure now, related to the special platform "Goldilocks Analogue". So, somehow I've not got the language to get the variant files for Goldilocks Analogue properly installed. My attempt to get it right is here... thoughts? Perhaps it needs to say below instead? package: Goldilocks:avr |
My first thought was that it was a problem in the string quoting of |
The answer is in the board name
- board: Goldilocks:avr:"Goldilocks Analogue"
+ board: Goldilocks:avr:goldilocks_analogue |
Perfect (nearly, just needed to add the SD library). But, TBH, I've no idea why the board is referred to as Anyway. Fixed and green tick. ✔️ |
I couldn't say how any of the internals work; my knowledge of architectures/platforms/boards extends only as far as knowing what strings to send to the Thanks for helping me find a few ways to improve this! |
The
EXPECT_*
environment variables are felt by the program as eithernil
or non-nil, which means that bothtrue
andfalse
in the action config will evaluate to non-empty strings.... effectivelytrue
. This had the effect of expecting unit tests when none should be expected.