Skip to content

Invalidate maybe-impure function return values after impure method/static calls #28639

Invalidate maybe-impure function return values after impure method/static calls

Invalidate maybe-impure function return values after impure method/static calls #28639

Triggered via pull request May 15, 2026 08:52
Status Cancelled
Total duration 2m 32s
Artifacts 2

phar.yml

on: pull_request
integration-tests  /  Check PHAR checksum
11s
integration-tests / Check PHAR checksum
Download base SHA PHAR
0s
Download base SHA PHAR
extension-tests  /  Check PHAR checksum
4s
extension-tests / Check PHAR checksum
other-tests  /  Check PHAR checksum
12s
other-tests / Check PHAR checksum
Commit PHAR
0s
Commit PHAR
Matrix: integration-tests / integration-run-phpstan
integration-tests  /  PMMP Tests
0s
integration-tests / PMMP Tests
Matrix: integration-tests / integration-tests
Checksum PHAR
Checksum PHAR
PHAR Prefix Diff
0s
PHAR Prefix Diff
Matrix: extension-tests / tests-extensions
Matrix: other-tests / Other Tests
integration-tests  /  Integration - Update baselines
0s
integration-tests / Integration - Update baselines
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 3 warnings
extension-tests / Check PHAR checksum
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
extension-tests / Check PHAR checksum
A task was canceled.
integration-tests / Check PHAR checksum
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
other-tests / Check PHAR checksum
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
Compile PHAR
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
Compile PHAR
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
Compile PHAR
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
Compile PHAR
Canceling since a higher priority waiting request for phar-refs/pull/5667/merge exists
Compiler Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36, shivammathur/setup-php@44454db4f0199b8b9685a5d763dc37cbf79108e1, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
integration-tests / Check PHAR checksum
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
other-tests / Check PHAR checksum
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
phar-file
3.75 MB
sha256:e3c4ba832cd231a772f8d9ab36c8acb2b965fa1a5c206e3d35cdd01ed4b08f66
phar-file-checksum
3.75 MB
sha256:9e332729cc4ba8cf5a6dddfefad39cb14ee0e87999c277bc5f14727844deb75b