Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub actions: add new automation to limit directory sizes #17928

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

DanielEScherzer
Copy link
Contributor

After discovering in August that Zend/tests had over 2500 entries, and that GitHub limits the display to only the first 1000 entries, I filed GH-15631 and sent a whole slew of patches to split up that directory and organize the tests a bit better. After the most recent patch, GH-17920, there are now once again fewer than 1,000 entries in that directory (for what seems to be the first time since the PHP 5.3 development cycle).

Add a new GitHub action to the test suite that will ensure that no directory gets above 1,000 items - while the Zend/tests directory was the only one that had already hit that limit, there isn't much harm in checking all of the directories, and some of the extensions have hundreds of tests already and could conceivably hit the limit at some point.

Closes GH-15631

After discovering in August that Zend/tests had over 2500 entries, and that
GitHub limits the display to only the first 1000 entries, I filed phpGH-15631 and
sent a whole slew of patches to split up that directory and organize the tests
a bit better. After the most recent patch, phpGH-17920, there are now once again
fewer than 1,000 entries in that directory (for what seems to be the first time
since the PHP 5.3 development cycle).

Add a new GitHub action to the test suite that will ensure that no directory
gets above 1,000 items - while the Zend/tests directory was the only one that
had already hit that limit, there isn't much harm in checking all of the
directories, and some of the extensions have hundreds of tests already and
could conceivably hit the limit at some point.

Closes phpGH-15631
@TimWolla TimWolla removed their request for review February 25, 2025 17:57
Copy link
Member

@iluuu1994 iluuu1994 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm meh on this in general. But in terms of CI, this should be its own workflow. There's no reason to check this for every job.

@iluuu1994 iluuu1994 requested a review from Girgias February 25, 2025 17:59
@Girgias
Copy link
Member

Girgias commented Feb 25, 2025

I'm not sure if a CI action is that useful? This might trigger in master when merging up bug fixes, which is not something we really want.

Zend/tests is probably the only folder that will ever have this issue, even the mysqli extension which has 500 tests is nowhere near that limit, and going forward any new feature should have their tests in a subfolder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Organize Zend/tests/*.phpt tests into subdirectories for easier navigation
3 participants