Skip to content

fix: GSuite data only populated on match #2429

fix: GSuite data only populated on match

fix: GSuite data only populated on match #2429

Triggered via pull request August 22, 2023 12:29
Status Failure
Total duration 1m 52s
Artifacts

test_suite.yml

on: pull_request
linter
1m 8s
linter
unit-and-integration-tests
1m 34s
unit-and-integration-tests
unit-and-integration-tests-neo4j5
1m 38s
unit-and-integration-tests-neo4j5
build-dist-docker-image
1m 13s
build-dist-docker-image
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
linter
Process completed with exit code 1.
unit-and-integration-tests
Process completed with exit code 2.
unit-and-integration-tests-neo4j5
Process completed with exit code 2.
build-dist-docker-image
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
unit-and-integration-tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
unit-and-integration-tests-neo4j5
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/