-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Ability to report processing time for each rule-per-file #4728
Comments
@mvorisek how would you imagine this to be done? |
@kubawerlos Very simple, measure rule apply time and then report the rule name, file name and the elapsed time if the elapsed time is greater than some treshold. Note, that this feature request is for reporting AFTER rule is executed. To discover rules that never finish or take very long time use verbose log, as there is no way (in single non-async thread) to display some message during the rule execution. For verbose logging, see #4372 What do you think? |
Rulesets or just rules? I was thinking once about adding something here: https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/v2.16.1/src/Runner/Runner.php#L150 Maybe some events before starting fixing a file and after finishing. |
You are right, rule not ruleset (I also updated the comment above to prevent any misunderstanding.)
👍 Yes |
It seems that verbose level (like
|
This PR was merged into the 2.16 branch. Discussion ---------- remove not supported verbose options #4728 (comment) Commits ------- 749c63a remove not supported verbose options
closing as performance issues are currently rarely problematic |
I am reopening this issue as when introducing PHP CS Fixer to some larger project it has to be rerun localy many times and if I would be able to list slow rules, it would help - save developer time - to disable them temporary. |
I've renamed the issue as it has nothing to do with tests 😉. |
Since this issue has not had any activity within the last 90 days, I have marked it as stale. The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way. You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point. I will close it if no further activity occurs within the next 30 days. |
not stale |
Since this issue has not had any activity within the last 90 days, I have marked it as stale. The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way. You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point. I will close it if no further activity occurs within the next 30 days. |
The fact this was automatically closed doesn't mean that the idea got rejected - it simply didn't get any priority for way too long to keep it open. If you're still interested in this, please let as know, we can consider re-opening it. |
This is a feature request to show slow tests like phpunit with
johnkary/phpunit-speedtrap
.Usecase: to quickly identify issues like #4656
The text was updated successfully, but these errors were encountered: