AppVeyor: Reduce upload_max_filesize below PHP_INT_MAX #42629
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes from #42618 made the tests on AppVeyor fail. The reason is that the test depends on the php.ini setting
upload_max_filesize
. The test picks the highest integer value available (PHP_INT_MAX
), assuming that this value is higher thanupload_max_filesize
in Bytes. On AppVeyor, we test with a 32bit build of PHP and aupload_max_filesize
setting of4G
. The fact that 4 Gigabytes in Bytes produce a number that cannot be represented with a 32bit integer contradicts with that assumption.This PR lowers
upload_max_filesize
to1G
so that we have a chance to test with integer values that are higher than this setting.