Attempt to update to FreeBSD 14.4.#23350
Conversation
|
It looks there are some warnings that need to be addressed due to changes that come with upgrading cross-platform-actions. But on top of that, it looks like there's a new test suite failure that I'm going to need to investigate. I'm not seeing that failure locally on FreeBSD 15 (though I get an error from valgrind about it trying to use unimplemented functionality, which I haven't seen previously), but my laptop is still on FreeBSD 14 IIRC. So, I'll try to find time to try it there after I get some sleep. |
|
I mentioned this to Adam elsewhere, but I'll mention it here for anyone else who might see the PR, but when I ran the test suite locally on my laptop with FreeBSD 14.3, it passed. I haven't tried 14.4 yet, because the drives proceeded to go south during that process, but since Adam has now tried this with FreeBSD 14.3, and it failed there too, that would indicate that it's not the case that 14.3 works and 14.4 does not. Presumably, either there is a difference in the environment, or I didn't run the tests in quite the same way. |
|
The CI logs point to a failure here: https://github.com/dlang/dmd/blob/master/compiler/test/dshell/dwarf.d#L57 I recall FreeBSD deprecating GCC in favour of LLVM in recent years. GNU's objdump puts the version on the first line, but LLVM's puts it on the second line - vs My guess is that objdump is LLVM's on the systems that are failing, and GNU's on the systems that aren't. Can you confirm? |
No description provided.