- Issue created by @alexpott
- Status changed to Needs review
12 months ago 9:32am 12 February 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
I've made this major because this will lead to contrib and custom tests failing.
- Status changed to RTBC
12 months ago 10:03am 12 February 2024 - 🇮🇹Italy mondrake 🇮🇹
Serms OK for now. A possible follow up is to make the timeout dependent on an env variable.
- Status changed to Needs work
12 months ago 10:11am 12 February 2024 - 🇬🇧United Kingdom longwave UK
Turns out the default is 60 seconds, which makes all our tests fail now.
- Status changed to Needs review
12 months ago 10:31am 12 February 2024 - 🇮🇹Italy mondrake 🇮🇹
$process->setTimeout(NULL);
should do, for it does not set any time limit to the process execution.https://github.com/symfony/symfony/blob/7.0/src/Symfony/Component/Proces...
- Status changed to RTBC
12 months ago 10:47am 12 February 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
Thanks @mondrake for fixing it to have an unlimited timeout - yeah 60 seconds was just not going to cut it :D
- Status changed to Fixed
12 months ago 10:55am 12 February 2024 -
longwave →
committed 75f85d81 on 11.x
Issue #3420765 by alexpott, mondrake: Remove new test timeout
-
longwave →
committed 75f85d81 on 11.x
Automatically closed - issue fixed for 2 weeks with no activity.