Thread overview
[Issue 20999] autotester for Darwin_64_64 randomly times out and fails
Jul 01, 2020
Walter Bright
Aug 05, 2020
Vladimir Panteleev
Nov 06, 2022
Dennis
Dec 17, 2022
Iain Buclaw
Jan 17, 2023
Iain Buclaw
July 01, 2020
https://issues.dlang.org/show_bug.cgi?id=20999

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |TestSuite

--
August 05, 2020
https://issues.dlang.org/show_bug.cgi?id=20999

Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dlang-bugzilla@thecybershad
                   |                            |ow.net

--- Comment #1 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
This sucks, it looks like it's hitting a deadlock right away. Might indicate a real race condition somewhere. I think in case of timeout, we should print the stack trace of all threads/processes, or something like that.

--
August 05, 2020
https://issues.dlang.org/show_bug.cgi?id=20999

moonlightsentinel@disroot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |moonlightsentinel@disroot.o
                   |                            |rg

--- Comment #2 from moonlightsentinel@disroot.org ---
(In reply to Vladimir Panteleev from comment #1)
> This sucks, it looks like it's hitting a deadlock right away. Might indicate a real race condition somewhere. I think in case of timeout, we should print the stack trace of all threads/processes, or something like that.

IIRC it's a file locking issue somewhere inside phobos/the system library triggered by the second invocation of `build.d`. I implemented a workaround when we finalized the transition to `build.d` which apparently stopped working some time ago.

I'll try to find a better solution.

--
November 06, 2022
https://issues.dlang.org/show_bug.cgi?id=20999

Dennis <dkorpel@live.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dkorpel@live.nl

--- Comment #3 from Dennis <dkorpel@live.nl> ---
Does this still happen?

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=20999

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P3

--
January 17, 2023
https://issues.dlang.org/show_bug.cgi?id=20999

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ibuclaw@gdcproject.org
         Resolution|---                         |WONTFIX

--- Comment #4 from Iain Buclaw <ibuclaw@gdcproject.org> ---
The Auto-tester itself has been taken down.

--