Excerpts from Iain Buclaw's message of September 5, 2025 6:45 pm:
> Excerpts from Iain Sandoe's message of September 3, 2025 9:59 pm:
>>
>>
>>> On 3 Sep 2025, at 20:54, Iain Buclaw wrote:
>>>
>>> Excerpts from Iain Buclaw's message of September 3, 2025 9:19 pm:
Excerpts from Rainer Orth's
> On 5 Sep 2025, at 17:45, Iain Buclaw wrote:
>
> Excerpts from Iain Sandoe's message of September 3, 2025 9:59 pm:
>>
>>
>>> On 3 Sep 2025, at 20:54, Iain Buclaw wrote:
>>>
>>> Excerpts from Iain Buclaw's message of September 3, 2025 9:19 pm:
Excerpts from Rainer Orth's message of Se
Excerpts from Iain Sandoe's message of September 3, 2025 9:59 pm:
>
>
>> On 3 Sep 2025, at 20:54, Iain Buclaw wrote:
>>
>> Excerpts from Iain Buclaw's message of September 3, 2025 9:19 pm:
>>> Excerpts from Rainer Orth's message of September 3, 2025 10:20 am:
>>
>> I regularly (but not
Excerpts from Iain Buclaw's message of September 3, 2025 9:19 pm:
> Excerpts from Rainer Orth's message of September 3, 2025 10:20 am:
I regularly (but not always) see timeouts on Solaris, both on sparc and
x86:
WARNING: libphobos.gc/forkgc2.d execution test program timed
> On 3 Sep 2025, at 20:54, Iain Buclaw wrote:
>
> Excerpts from Iain Buclaw's message of September 3, 2025 9:19 pm:
>> Excerpts from Rainer Orth's message of September 3, 2025 10:20 am:
>
> I regularly (but not always) see timeouts on Solaris, both on sparc and
> x86:
>
>
Excerpts from Rainer Orth's message of September 3, 2025 10:20 am:
>>>
>>> I regularly (but not always) see timeouts on Solaris, both on sparc and
>>> x86:
>>>
>>> WARNING: libphobos.gc/forkgc2.d execution test program timed out.
>>> FAIL: libphobos.gc/forkgc2.d execution test
>>> WARNING: libpho
> On 3 Sep 2025, at 09:20, Rainer Orth wrote:
>
> Hi Iain,
>
>>> On 2 Sep 2025, at 15:25, Rainer Orth wrote:
>>
> What about Solaris and *BSD. Are there any outstanding PRs for druntime
> hanging
> on those ports too? Or is specific to Darwin (or possibly emutls?).
Hi Iain,
>> On 2 Sep 2025, at 15:25, Rainer Orth wrote:
>
What about Solaris and *BSD. Are there any outstanding PRs for druntime
hanging
on those ports too? Or is specific to Darwin (or possibly emutls?).
>>>
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
>>>
>>> say
Hi Iain,
>> What about Solaris and *BSD. Are there any outstanding PRs for druntime
>> hanging
>> on those ports too? Or is specific to Darwin (or possibly emutls?).
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
>
> says darwin and i686-linux (so my exclusion of linux is not right), b
Hi Iain
> On 2 Sep 2025, at 15:25, Rainer Orth wrote:
>>> What about Solaris and *BSD. Are there any outstanding PRs for druntime
>>> hanging
>>> on those ports too? Or is specific to Darwin (or possibly emutls?).
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944
>>
>> says darwin a
cc-ing Rainer
> On 2 Sep 2025, at 14:47, Iain Buclaw wrote:
>
> Excerpts from Iain Sandoe's message of September 1, 2025 6:23 pm:
>> In use for 2 years or so on Darwin branches, OK for trunk?
>> thanks
>> Iain
>>
>> --- 8< ---
>>
>> The collect fork version has two issues on Darwin, first that
Excerpts from Iain Sandoe's message of September 1, 2025 6:23 pm:
> In use for 2 years or so on Darwin branches, OK for trunk?
> thanks
> Iain
>
> --- 8< ---
>
> The collect fork version has two issues on Darwin, first that it seems
> to hang quite frequently and second that ___fork() is not avai
In use for 2 years or so on Darwin branches, OK for trunk?
thanks
Iain
--- 8< ---
The collect fork version has two issues on Darwin, first that it seems
to hang quite frequently and second that ___fork() is not available on
all OS versions. The remedy here is to avoid its use, for now.
---
...
13 matches
Mail list logo