Seeing so many commits that are "skip failing test" is a very strong code smell.

Yes, but it is often a sad reality of trying to run projects mainly written for glibc on musl. Not many people write portable C these days.

It's still the wrong way to go about things. Tests are there for a reason, meaning if they fail you should try to understand them to the point where you can fix the problem (broken test or actual bug) instead of just wantonly distabling tests until you get a green light.

> do you see anything suspicious

No.

> libunistring could also be affected as that has also been pushed there

What do you mean by "that"?