Skip to content
CI

IBX-7418: Added ContentNameCriterion #1532

Sign in to view logs

IBX-7418: Added ContentNameCriterion

IBX-7418: Added ContentNameCriterion #1532

Re-run triggered December 22, 2023 12:11
@ciastektkciastektk
#312
ibx-7418-added-content-name-criterion
Status Failure
Total duration 10m 19s
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

21 errors and 28 warnings
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.1)
Process completed with exit code 1.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (7.4)
Process completed with exit code 1.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0): tests/integration/Core/Repository/SearchServiceContentNameTest.php#L372
Failed asserting that two arrays are equal.
Unit tests & SQLite integration tests (8.0)
Process completed with exit code 1.
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/
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)
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)
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/
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.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.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 (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)
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 `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.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/