When running tests with xdebug enabled (in develop mode in my case), \AsyncAws\Core\Tests\Unit\ResultTest::testWaitWithExceptionOnDestruct fails because the Result is not destructed inside the test.
My debugging made me discover that the UnparsableResponse exception that is used by the AwsErrorFactory layer and caught in the Response object is somehow increasing the refcount of the Result object (probably due to its stack trace) when xdebug is loaded even when that exception goes out of scope.
When running tests with xdebug enabled (in
developmode in my case),\AsyncAws\Core\Tests\Unit\ResultTest::testWaitWithExceptionOnDestructfails because the Result is not destructed inside the test.My debugging made me discover that the
UnparsableResponseexception that is used by the AwsErrorFactory layer and caught in the Response object is somehow increasing the refcount of the Result object (probably due to its stack trace) when xdebug is loaded even when that exception goes out of scope.