IBX-6773: Bookmarks for non accessible contents cause exception #1036
vidarlci.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
Annotations
9 errors and 24 warnings
|
Unit tests & SQLite integration tests (8.0):
eZ/Bundle/EzPublishDebugBundle/Twig/DebugTemplate.php#L79
Return type string of method eZ\Bundle\EzPublishDebugBundle\Twig\DebugTemplate::doDisplay() is not covariant with return type iterable of method Twig\Template::doDisplay().
|
|
Unit tests & SQLite integration tests (8.0)
Process completed with exit code 1.
|
|
Unit tests & SQLite integration tests (8.1):
eZ/Bundle/EzPublishDebugBundle/Twig/DebugTemplate.php#L79
Return type string of method eZ\Bundle\EzPublishDebugBundle\Twig\DebugTemplate::doDisplay() is not covariant with return type iterable of method Twig\Template::doDisplay().
|
|
Unit tests & SQLite integration tests (8.1)
Process completed with exit code 1.
|
|
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ParseError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "syntax error, unexpected 'LoggerInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)" at
|
|
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ParseError" matches expected exception "Exception". Message was: "syntax error, unexpected 'LoggerInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)" at
|
|
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ParseError" matches expected exception "Exception". Message was: "syntax error, unexpected 'LoggerInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)" at
|
|
Unit tests & SQLite integration tests (7.3)
Failed asserting that exception of type "ParseError" matches expected exception "eZ\Publish\API\Repository\Exceptions\InvalidArgumentException". Message was: "syntax error, unexpected 'LoggerInterface' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST)" at
|
|
Unit tests & SQLite integration tests (7.3)
Process completed with exit code 2.
|
|
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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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.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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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 (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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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/
|
|
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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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/
|
|
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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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/
|
|
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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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 (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 following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-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 (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.1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, ramsey/composer-install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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/
|