- Issue created by @mondrake
- Status changed to Needs review
12 months ago 3:58pm 29 January 2024 - Status changed to RTBC
12 months ago 4:13pm 29 January 2024 - 🇫🇷France andypost
I recall we fixed it in other parts of core to prepare to next SF version
-
longwave →
committed b8a5017e on 11.x
Issue #3417805 by mondrake: Use Symfony Process to spawn subprocesses in...
-
longwave →
committed b8a5017e on 11.x
- Status changed to Fixed
12 months ago 2:54pm 2 February 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
We shouldn't be setting a timeout on test arbitrarily. We have no idea how long contrib and custom tests take (on whichever CI run on or a local machine). This change is disruptive. It also makes a long debugging session annoying.
If we want to add a timeout here - it should be configurable by an environmental variable. And the default probably should be no timeout.
- 🇬🇧United Kingdom longwave UK
Let's just remove the
setTimeout()
for now then? - 🇬🇧United Kingdom alexpott 🇪🇺🌍
@longwave yep - opened 🐛 Remove new test timeout Needs review to address.
Automatically closed - issue fixed for 2 weeks with no activity.