zappolowski

As I've said the culprit is not Arch, but my login-shell, which is `fish`, which is (intentionally) not POSIX-compatible. I've created two (hopefully) portable containers to verify this (TBH it...

You've run the tests on `libtmux`, but the issue is on `tmuxp`. :smiley: But yeah, that error I also get on `libtmux` but I couldn't figure out how to make...

Yes, these are the same tests failing for me.

@bebehei The error is caused but what I described in [this comment](https://github.com/dunst-project/docker-images/pull/7#issuecomment-1950986704). I've added [this commit](https://github.com/dunst-project/docker-images/pull/7/commits/52541a3da3ddd2e616aa25e40472c8f58e8e5238) to make it work locally. So, something like ```patch diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index...

@bebehei I took another look into the latest build failures and it's rather wild. The Debian bookworm image currently lacks a required package `libclang-rt-dev`, but even when added it's not...

@bebehei I figured it out ... at least I cannot reproduce the failure locally anymore. 1. Update the `debian-bookworm` image ... see [this PR](https://github.com/dunst-project/docker-images/pull/11) 2. add `--coverage` to `CFLAGS`, e.g....

I've just updated the debian-bookworm image and it seems like it works without addition of `--coverage` ... for whatever reason. Currently the pipeline is green, but some tests and alpine...

> I will do some fixes and merge it then 👍 I wouldn't merge as long as CI doesn't work properly. I also accidentally merged a branch yesterday - but...

@bynect As I've merged the new pipeline you could rebase this branch and then hopefully we can go forward merging it.

Yes, just go ahead and merge it.