On 16/01/2026 11:07 PM, confuzzled wrote:
On 1/14/26 1:57 PM, Richard (Rikki) Andrew Cattermole wrote:
> On 14/01/2026 3:56 PM, confuzzled wrote:
>>
>> I think there is something corrupted in the build system. I just built
>> the v2.112.0 tag on my intel MacBook Pro running 15.5 and it worked
>> fine. Then I upgraded to 26.2 and it still works fine.
>
> Building, and passing testsuite are two very different things.
And still that implied rigor that is inherently built into the official
building process did NOTHING to prevent it from delivering a product
that is 100% broken on macOS. Prey tell, how many tests in said suite
did it pass?
But maybe I am misunderstanding you. Is something like this (see
attached log) what you are referring to or is there some other specific
testsuite that it must pass to be considered a successful build?
Look, all I'm saying is that if I can build the compiler and use it to
compile itself on macOS, then there is something wrong with the way it
is being built in the release process. I am not in any way suggesting
that v2.112.0 does not introduce regressions or other bugs.
Note: I couldn't post complete log for DMD/DRuntime/Phobos because the
exceed newsgroup size limitations.
It is not broken on older versions of MacOS and is passing on them.
We've been having a lot of trouble with MacOS since about version 11,
and that is just from what little I remember. Apple keeps breaking stuff
that should never be broken. Every CI bump has resulted in compiler or
druntime needing fixing something fundamental.
It was not compiling or passing the testsuite as of two months ago when
I tried to bump the CI runner to 15. For both dmd-master and ldc-latest.
When it failed to build and pass the testsuite on 15 I reported it at
the monthly meeting.
Dmd's testsuite comprises tests that were added because the compiler did
the wrong thing in the past. If you cannot pass it, you do not have a
functioning D compiler.
You seem to have gotten further than what I did two months ago, so that
is something.
