Ian

I made some crappy ascii art, if that helps. ``` ___ ╭───┸──╮ ╷┌╯CHECK ╰╮╭╮ ┝┥ ENGINE └╯│ ╵└─╮ ╭╮│ └──────╯└╯ ___ ╭───┸─╮ ╷┌╯ ╰─╮╭╮ ┝┥ CHECK └╯│ ╵└─╮ENGINE╭╮│ └──────╯└╯ ```...

This is great actually. Knowing that I can depend on `file`/`line` for warnings (but not for errors at all) means my ingestion algorithm is as complete as it can ever...

Is this what you're looking for? https://github.com/emaculation/shoebill#how-to-build-shoebill

Please advise on whether this issue should be copied to https://github.com/emaculation/shoebill

@shiftkey do you think this merits adding the `pinned` label, as the bot suggests? Or has the underlying quirk about the `repo` scope been resolved upstream?

> You need to add an "options: --privileged" to the CI yml under your container. Can you show an example of this in context?

Hello, For your consideration, I've implemented this "unit tests on CI" by borrowing heavily from your unit testing framework. It's available as a ruby gem: https://github.com/ifreecarve/arduino_ci Example of the `arduino_ci_remote.rb`...

A few things are missing from ArduinoUnit that prevent it from being used for CI. (Although, for each of the following, it's possible I'm missing something obvious and would greatly...

That's your call. I'm of the opinion (shared by [others](https://stackoverflow.com/a/11437456/2063546)) that unit tests shouldn't run in the target environment, because at that point they cease to be _unit_ tests --...

AUnit does not "provide a sample project with continuous integration". `arduino_ci` does. You and I agree on structuring classes for testability, but that's not the point of my example. `arduino_ci`'s...