Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 3.7.1

Request #18252 PHP_Timer output in report
Submitted: 2011-02-08 17:05 UTC
From: sebastian Assigned: squiz
Status: Closed Package: PHP_CodeSniffer (version 1.3.0RC2)
PHP Version: 5.3.5 OS: Linux
Roadmaps: (Not assigned)    

 [2011-02-08 17:05 UTC] sebastian (Sebastian Bergmann)
Description: ------------ Using --report-full and --report-source leads to having the PHP_Timer output in the respective report fies (and not on stdout).


 [2011-02-15 10:51 UTC] squiz (Greg Sherwood)
-Type: Bug +Type: Feature/Change Request -Assigned To: +Assigned To: squiz
This is a result of how PHP_Timer integration works. It is actually part of some select reports rather than something that runs at the end. Basically, an added feature for reports that are designed to be viewed rather than processed. The reason for this implementation was that the output of PHPCS for some report types should not have any trailing data (I'm thinking CSV, XML etc). Reporting has a changed a bit in PHPCS recently, so this may not be such a big deal any more as there are possible alternatives. It would need to be looked at again to see if the implementation can be redone.
 [2011-04-07 11:56 UTC] squiz (Greg Sherwood)
-Status: Assigned +Status: Open
 [2011-04-15 06:15 UTC] squiz (Greg Sherwood)
-Status: Open +Status: Closed -Assigned To: +Assigned To: squiz
This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better. PHP_Timer output is no longer printed to files and will be printed to the screen only if printing a screen-based report (like the full and summary reports) or if you are printing all reports to files.