• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

PHPCSStandards / PHP_CodeSniffer / 43787864262
79%
master: 79%

Build:
Build:
LAST BUILD BRANCH: big-switch
DEFAULT BRANCH: master
Ran 16 Nov 2026 01:44AM UTC
Jobs 8
Files 310
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

16 Nov 2026 01:42AM UTC coverage: 78.66%. Remained the same
43787864262

push

github

web-flow
E2E tests: fix failure after #php2shell patch (#1516)

History

PHPCS contains a custom error message which will be displayed to end-users if PHP runs out of memory during the execution of a PHPCS scan. This message gives some helpful advise on how to raise the memory for a PHPCS run.
This message was introduced in PHPCS 3.7.2 in response to PHP intermittently not showing the Fatal error for being out of memory, which left users with no clue as to why their PHPCS run was halted mid-scan.

This custom error message display was safeguarded via the BashUnit End to End tests since PHPCS 3.13.5.

Current problem

One of the recent #PHP2Shell vulnerabilities was related to the way PHP handles Out of Memory errors.

Now for the officially patched PHP versions (8.2 - 8.6), everything continues to work as expected and the custom message is still displayed as expected.
However, both PHPCS 3.x as well as 4.x, still support PHP versions which are no longer supported by the PHP project and the custom message display is currently broken on those versions.

Analysis

For those unsupported PHP versions which are used in the CI of the project, shivammathur from the `setup-php` action runner has back-ported a minimal patch for the OOM issue to ensure those PHP versions when used in CI are not vulnerable anymore. :tada: Huge kudos to shivammathur for doing that!

This minimal patch, however, breaks our custom message because it no longer runs registered shutdown functions when an out of memory error has been detected. This feels like a perfectly acceptable choice for the backport to unsupported PHP versions, so I'm not going to challenge that.

However, that does still leave us with broken test expectations.

The fix

The current commit changes the test expectations based on the detected PHP version:
* The PHPCS E2E OOM tests will now always verify if a PHP native "Fatal error: Allowed memory size" error is displayed.
* Additionally, for those PHP versions which support... (continued)

25341 of 32216 relevant lines covered (78.66%)

74.93 hits per line

Jobs
ID Job ID Ran Files Coverage
1 os-ubuntu-latest-php-5.4-custom-ini-false - 43787864262.1 16 Nov 2026 02:14AM UTC 310
72.83
GitHub Action Run
2 cbf-os-ubuntu-latest-php-5.4-custom-ini-false - 43787864262.2 16 Nov 2026 02:14AM UTC 310
1.43
GitHub Action Run
3 os-windows-latest-php-5.5-custom-ini-false - 43787864262.3 16 Nov 2026 01:46AM UTC 310
2.24
GitHub Action Run
4 cbf-os-ubuntu-latest-php-8.5-custom-ini-false - 43787864262.4 16 Nov 2026 01:46AM UTC 310
1.84
GitHub Action Run
5 cbf-os-ubuntu-latest-php-7.2-custom-ini-true - 43787864262.5 16 Nov 2026 01:47AM UTC 310
0.89
GitHub Action Run
6 os-windows-latest-php-8.5-custom-ini-false - 43787864262.6 16 Nov 2026 01:44AM UTC 310
2.49
GitHub Action Run
7 os-ubuntu-latest-php-7.2-custom-ini-true - 43787864262.7 16 Nov 2026 01:47AM UTC 310
71.95
GitHub Action Run
8 os-ubuntu-latest-php-8.5-custom-ini-false - 43787864262.8 16 Nov 2026 01:46AM UTC 310
73.93
GitHub Action Run
Source Files on build 43787864262
  • Tree
  • List 310
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #43787864262
  • 8265ce94 on github
  • Prev Build on 3.x (#32430256266)
  • Next Build on 3.x (#43794277826)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc