Add recipe for Yocto ptests & run in GitHub Actions CI#7
Conversation
Builds a qemux86-64 Yocto image via kas, boots it under QEMU with slirp networking, and runs ptest-runner gpiod-sysfs-proxy over SSH. Signed-off-by: Christopher Obbard <christopher.obbard@linaro.org>
|
Nice, is this free? Can I do the same for libgpiod core? |
Signed-off-by: Christopher Obbard <christopher.obbard@linaro.org>
yep, for open source projects. Building a yocto image and running it in CI is a bit of an antipattern though |
|
I don't see a different way of testing it without being able to run a custom kernel with |
Add build_system: oe to the kas config so kas 4.x can locate the oe-init-build-env script in the poky checkout. Signed-off-by: Christopher Obbard <christopher.obbard@linaro.org>
24aafcb to
77a3d3f
Compare
Yeah, I agree. Currently it fails with: Don't really have time right now to investigate it, but will come back to it soonish. |
Signed-off-by: Christopher Obbard <christopher.obbard@linaro.org>
|
@brgl I managed to build an image with the test deps, but the test always seems to pass. Can you help me figure out what I am doing wrong ? I build & run with: |
You mean they pass with pyfuse3? The setup looks correct. What's the output from the test script? |
The test doesn't seem to use the local checkout of this repo :/. Not sure how to fix that, any pointers welcome! |
How about not installing the |
Initial commit. May be a bit useless as it takes a while to build the image, but we shall see.