Skip to content

Build on php 8.4

Build on php 8.4 #73

Triggered via pull request November 3, 2024 20:31
@jaapiojaapio
synchronize #375
build-php84
Status Failure
Total duration 1m 28s
Artifacts

integrate.yaml

on: pull_request
Unit test  /  Supported Versions Matrix
3s
Unit test / Supported Versions Matrix
Code Coverage  /  Code Coverage
16s
Code Coverage / Code Coverage
BC Check
7s
BC Check
Matrix: Coding Standards / Coding Standards
Matrix: Dependency analysis / Dependency Analysis
Matrix: Lint root / Lint yaml & Composer
Matrix: Static analysis / Static Code Analysis
Matrix: Unit test / Tests
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
RiskyTruthyFalsyComparison: src/DocBlock/ExampleFinder.php#L47
src/DocBlock/ExampleFinder.php:47:13: RiskyTruthyFalsyComparison: Operand of type array<array-key, string>|null contains type array<array-key, string>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/ExampleFinder.php#L115
src/DocBlock/ExampleFinder.php:115:13: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/ExampleFinder.php#L125
src/DocBlock/ExampleFinder.php:125:18: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/Serializer.php#L85
src/DocBlock/Serializer.php:85:23: RiskyTruthyFalsyComparison: Operand of type int|null contains type int, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/StandardTagFactory.php#L169
src/DocBlock/StandardTagFactory.php:169:31: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/StandardTagFactory.php#L176
src/DocBlock/StandardTagFactory.php:176:13: RiskyTruthyFalsyComparison: Operand of type false|int<0, max> contains type int<0, max>, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/Tags/Deprecated.php#L65
src/DocBlock/Tags/Deprecated.php:65:13: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/Tags/Param.php#L163
src/DocBlock/Tags/Param.php:163:13: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/Tags/Property.php#L120
src/DocBlock/Tags/Property.php:120:13: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
RiskyTruthyFalsyComparison: src/DocBlock/Tags/PropertyRead.php#L120
src/DocBlock/Tags/PropertyRead.php:120:13: RiskyTruthyFalsyComparison: Operand of type null|string contains type string, which can be falsy and truthy. This can cause possibly unexpected behavior. Use strict comparison instead. (see https://psalm.dev/356)
BC Check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/