Tracing doesn't work in github CI #1
Description
Something is causing tracing to fail in github CI. For now the unit tests are disabled for this reason, but I've enabled them for testing in branch enable-tests-in-ci. An example CI test failure is here:
Actual:
----
status code: 1
std out:
std err:
Error: ESRCH
I believe this means the process is not found. I'm not sure if this is caused by the tracee process never starting, or dieing for some reason, or if something is just causing us to not be able to ptrace attach to it.
There are other test failures in the link above due to differences in the libc version on my development machine and the libc version on the machine in CI. That will also need to be resolved, but that is distinct from this. See #2.
I have tried running backlight in an ubuntu docker image (although my understanding is github CI doesn't use containers?) locally, and it works fine - although in that case I was testing a musl build so I could simply mount the target directory and run binaries built on my host machine.
The thing which is especially puzzling is that strace has a github CI pipeline which presumably uses the ptrace API (I haven't verified exactly what their github CI pipeline does) and it seems to work.