It looks like the darwin 32 release is broken at the phobos unittest stage. It would appear the breakage is in the uni.d debug step:
make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation fault: 11

I don't think it is the new uni module that is responsible, since it worked fine when it was merged.

I haven't pinned down which pull triggered the breakage, but I figure the first step to getting the release fixed is to announce it as broken. Or I should file a report instead?

On Monday, 12 August 2013 at 13:57:53 UTC, monarch_dodra wrote:
> It looks like the darwin 32 release is broken at the phobos unittest stage. It would appear the breakage is in the uni.d debug step:
> make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation fault: 11
>
> I don't think it is the new uni module that is responsible, since it worked fine when it was merged.
>
> I haven't pinned down which pull triggered the breakage, but I figure the first step to getting the release fixed is to announce it as broken. Or I should file a report instead?

Filed:
http://d.puremagic.com/issues/show_bug.cgi?id=10809

On topic, it would appear there is also a dmd regression:
make[1]: *** [test_results/runnable/argufilem.d.out] Error 1

Links:
http://d.puremagic.com/test-results/platform-history.ghtml?projectid=1&os=Darwin_32

12-Aug-2013 17:57, monarch_dodra пишет:
> It looks like the darwin 32 release is broken at the phobos unittest
> stage. It would appear the breakage is in the uni.d debug step:
> make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation
> fault: 11
>
> I don't think it is the new uni module that is responsible, since it
> worked fine when it was merged.
>
> I haven't pinned down which pull triggered the breakage, but I figure
> the first step to getting the release fixed is to announce it as broken.
> Or I should file a report instead?

That's right but ... In the phobos mailing list next time :)

-- 
Dmitry Olshansky

On 2013-08-12 15:57, monarch_dodra wrote:
> It looks like the darwin 32 release is broken at the phobos unittest
> stage. It would appear the breakage is in the uni.d debug step:
> make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation
> fault: 11
>
> I don't think it is the new uni module that is responsible, since it
> worked fine when it was merged.
>
> I haven't pinned down which pull triggered the breakage, but I figure
> the first step to getting the release fixed is to announce it as broken.
> Or I should file a report instead?

It should be reverted now. I change the compiler from GCC to Clang, apparently that didn't work out. Walter did fix a bunch of warnings tough :)

-- 
/Jacob Carlborg

On Tuesday, 13 August 2013 at 04:39:11 UTC, Dmitry Olshansky wrote:
> 12-Aug-2013 17:57, monarch_dodra пишет:
>> It looks like the darwin 32 release is broken at the phobos unittest
>> stage. It would appear the breakage is in the uni.d debug step:
>> make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation
>> fault: 11
>>
>> I don't think it is the new uni module that is responsible, since it
>> worked fine when it was merged.
>>
>> I haven't pinned down which pull triggered the breakage, but I figure
>> the first step to getting the release fixed is to announce it as broken.
>> Or I should file a report instead?
>
> That's right but ... In the phobos mailing list next time :)

Right... I'll do that next time.

On Tuesday, 13 August 2013 at 06:37:28 UTC, Jacob Carlborg wrote:
> On 2013-08-12 15:57, monarch_dodra wrote:
>> It looks like the darwin 32 release is broken at the phobos unittest
>> stage. It would appear the breakage is in the uni.d debug step:
>> make[1]: *** [generated/osx/debug/32/unittest/std/uni] Segmentation
>> fault: 11
>>
>> I don't think it is the new uni module that is responsible, since it
>> worked fine when it was merged.
>>
>> I haven't pinned down which pull triggered the breakage, but I figure
>> the first step to getting the release fixed is to announce it as broken.
>> Or I should file a report instead?
>
> It should be reverted now. I change the compiler from GCC to Clang, apparently that didn't work out. Walter did fix a bunch of warnings tough :)

Cool.

Thanks for the feedback. I closed the ticket then.