Skip to content

IBX-5388: Fixed performance issues of content updates after field changes #975

IBX-5388: Fixed performance issues of content updates after field changes

IBX-5388: Fixed performance issues of content updates after field changes #975

Triggered via pull request April 16, 2024 07:49
Status Failure
Total duration 9m 29s
Artifacts

ci.yaml

on: pull_request
Matrix: Unit tests & SQLite integration tests
Matrix: Run code style check
Matrix: Solr integration tests
Matrix: MySQL integration tests
Matrix: PostgreSQL integration tests
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 42 warnings
Run code style check (8.0)
Process completed with exit code 1.
Unit tests & SQLite integration tests (8.1)
Process completed with exit code 2.
Unit tests & SQLite integration tests (7.4)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.4)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.4)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.4)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\NotFoundException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.4)
Process completed with exit code 2.
Unit tests & SQLite integration tests (8.0)
Process completed with exit code 2.
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ArgumentCountError" matches expected exception "eZ\Publish\API\Repository\Exceptions\NotFoundException". Message was: "Too few arguments to function eZ\Publish\Core\Persistence\Legacy\Content\Mapper::__construct(), 3 passed and exactly 4 expected" at
Unit tests & SQLite integration tests (7.3)
Process completed with exit code 2.
Solr integration tests (7.4)
Process completed with exit code 2.
Solr integration tests (8.1)
Process completed with exit code 2.
Solr integration tests (8.0)
Process completed with exit code 2.
Run code style check (8.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Run code style check (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run code style check (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run code style check (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run code style check (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Run code style check (8.0): eZ/Publish/Core/Persistence/Legacy/Tests/Content/MapperTest.php#L1
Found violation(s) of type: single_blank_line_before_namespace
Run code style check (8.0): eZ/Publish/Core/Persistence/Legacy/Tests/Content/MapperTest.php#L1
Found violation(s) of type: ordered_imports
Run code style check (8.0): eZ/Publish/Core/Persistence/Legacy/Tests/Content/MapperTest.php#L1
Found violation(s) of type: binary_operator_spaces
Unit tests & SQLite integration tests (8.1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit tests & SQLite integration tests (8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests & SQLite integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (7.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit tests & SQLite integration tests (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests & SQLite integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (7.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (8.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit tests & SQLite integration tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests & SQLite integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Unit tests & SQLite integration tests (7.3)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit tests & SQLite integration tests (7.3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Unit tests & SQLite integration tests (7.3)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (7.4)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Solr integration tests (7.4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Solr integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (7.4)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (7.4)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.1)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Solr integration tests (8.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, ramsey/composer-install@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Solr integration tests (8.1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Solr integration tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Solr integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.0)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.1)
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.0)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Solr integration tests (8.1)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/