You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason the i368 with JIT enabled takes a very long time (multiple factors more than it used to) so it runs into the Azure Pipelines timeout. We can increase the timeout of course but the main question is why it's suddenly taking much longer. Looking at the commits it seems that this regression has been introduced in one of these commits:
Description
https://dev.azure.com/phpazuredevops/PHP/_build/results?buildId=27980&view=logs&j=43d0f663-eb3d-56b0-eec1-60eb19a0df04&t=a596a022-74ec-59c9-c5bc-5ce4dc18a2ef
For some reason the i368 with JIT enabled takes a very long time (multiple factors more than it used to) so it runs into the Azure Pipelines timeout. We can increase the timeout of course but the main question is why it's suddenly taking much longer. Looking at the commits it seems that this regression has been introduced in one of these commits:
I'll have time to bisect the commits on Thursday.
@dstogov FYI.
PHP Version
PHP 8.1 and master
Operating System
No response
The text was updated successfully, but these errors were encountered: