Thread overview
[Issue 20955] Test suite times out running tests in dmd/test, but leaves no clue which test hung
June 19
https://issues.dlang.org/show_bug.cgi?id=20955

Walter Bright <bugzilla@digitalmars.com> changed:

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

--- Comment #1 from Walter Bright <bugzilla@digitalmars.com> ---
https://auto-tester.puremagic.com/show-run.ghtml?projectid=1&runid=4088732&isPull=true

--
August 05
https://issues.dlang.org/show_bug.cgi?id=20955

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

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

--- Comment #2 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
Looking at the related code, it doesn't seem like any particular test timed out; rather, the entire test execution timed out.

https://github.com/braddr/at-client/blob/8a2a2743716fcfde13d5ab0856bd4b5a0e403851/src/driver-v5.sh#L235

It would be nice to have some timestamps displaying how long each step took. E.g., the output could be piped through the `ts` utility:

https://linux.die.net/man/1/ts

Here is a D implementation:

https://github.com/CyberShadow/misc/blob/master/ts.d

--
January 09
https://issues.dlang.org/show_bug.cgi?id=20955

Mathias LANG <pro.mathias.lang@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pro.mathias.lang@gmail.com
          Component|tools                       |dmd

--- Comment #3 from Mathias LANG <pro.mathias.lang@gmail.com> ---
Moving from tools to DMD.

--