Wooster

> I don't know how to add a test for a compile error. I see the tests in test/cases/compile_errors, but I don't know they work because they don't seem to...

Sorry, I think that was my intention originally but I somehow thought it wasn't really possible to add a test for this but now thanks to your reminder I realize...

Oh, yeah, that was why. The caret isn't included at all. I'm not sure if we wanna add a special feature to the test harness for a single test. If...

While working on a standalone test I found something else that that seems like a regression: ``` $ zig build-exe test/cases/compile_errors/invalid_byte.zig --color off test/cases/compile_errors/invalid_byte.zig:2:7: error: expected expression, found 'invalid bytes'...

`zig build test-standalone` is definitely passing for me locally on x86_64-linux but even that CI is failing here. I'll try to `continue` on `error.FileBusy` (like in `test/src/Cases.zig`) but other than...

Oh, those changes is probably also why the CI is failing because normal test cases also use `--color off` but now source lines etc. are included. Makes sense. Hmm, this...

You're right. I usually prefer doing it that way but I thought maybe it would be too long but I guess it's fine.

Just realized that the "setName, getName" test actually expects `error.Unsupported` specifically if we're using musl libc (and remember I removed the `else` for that). Again, am I wrong about this?...

Also, looking at the implementation of for example `pthread_getname_np` in musl libc (so doesn't that mean it does support it? My source is some patch that adds it from 2021),...

Ok, I think I got it now. It turned out to be a bit different from initially assumed. This time I've actually tested this locally as well so I am...