IBX-5705: Fixed InteractiveLoginToken using PostAuthenticationGuardToken #1259
Triggered via pull request
September 18, 2023 06:49
Status
Failure
Total duration
15m 4s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
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
Annotations
12 errors and 28 warnings
Unit tests & SQLite integration tests (8.0):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L1
Ignored error pattern #^Method Ibexa\\Core\\MVC\\Symfony\\Security\\InteractiveLoginToken\:\:__unserialize\(\) has parameter \$serialized with no type specified\.$# in path /home/runner/work/core/core/src/lib/MVC/Symfony/Security/InteractiveLoginToken.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.0):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L62
Offset 2 does not exist on array{0: string, 1: mixed, 2?: Symfony\Component\Security\Core\Authentication\Token\TokenInterface}.
|
Unit tests & SQLite integration tests (8.0):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L75
Method Ibexa\Core\MVC\Symfony\Security\InteractiveLoginToken::getOriginalToken() should return Symfony\Component\Security\Core\Authentication\Token\TokenInterface but returns Symfony\Component\Security\Core\Authentication\Token\TokenInterface|null.
|
Unit tests & SQLite integration tests (8.0)
Process completed with exit code 1.
|
Unit tests & SQLite integration tests (7.4):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L1
Ignored error pattern #^Method Ibexa\\Core\\MVC\\Symfony\\Security\\InteractiveLoginToken\:\:__unserialize\(\) has parameter \$serialized with no type specified\.$# in path /home/runner/work/core/core/src/lib/MVC/Symfony/Security/InteractiveLoginToken.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (7.4):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L62
Offset 2 does not exist on array{0: string, 1: mixed, 2?: Symfony\Component\Security\Core\Authentication\Token\TokenInterface}.
|
Unit tests & SQLite integration tests (7.4):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L75
Method Ibexa\Core\MVC\Symfony\Security\InteractiveLoginToken::getOriginalToken() should return Symfony\Component\Security\Core\Authentication\Token\TokenInterface but returns Symfony\Component\Security\Core\Authentication\Token\TokenInterface|null.
|
Unit tests & SQLite integration tests (7.4)
Process completed with exit code 1.
|
Unit tests & SQLite integration tests (8.1):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L1
Ignored error pattern #^Method Ibexa\\Core\\MVC\\Symfony\\Security\\InteractiveLoginToken\:\:__unserialize\(\) has parameter \$serialized with no type specified\.$# in path /home/runner/work/core/core/src/lib/MVC/Symfony/Security/InteractiveLoginToken.php was not matched in reported errors.
|
Unit tests & SQLite integration tests (8.1):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L62
Offset 2 does not exist on array{0: string, 1: mixed, 2?: Symfony\Component\Security\Core\Authentication\Token\TokenInterface}.
|
Unit tests & SQLite integration tests (8.1):
src/lib/MVC/Symfony/Security/InteractiveLoginToken.php#L75
Method Ibexa\Core\MVC\Symfony\Security\InteractiveLoginToken::getOriginalToken() should return Symfony\Component\Security\Core\Authentication\Token\TokenInterface but returns Symfony\Component\Security\Core\Authentication\Token\TokenInterface|null.
|
Unit tests & SQLite integration tests (8.1)
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.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.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.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/
|
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/
|
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/
|