Skip to content

fix(metadata-io): in Neo4j service use proper algorithm to get lineage #21602

fix(metadata-io): in Neo4j service use proper algorithm to get lineage

fix(metadata-io): in Neo4j service use proper algorithm to get lineage #21602

Triggered via pull request August 22, 2023 14:59
Status Cancelled
Total duration 9m 56s
Artifacts 2

build-and-test.yml

on: pull_request
quickstart-compose-validation
25s
quickstart-compose-validation
event-file
2s
event-file
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 9 warnings
quickstart-compose-validation
Process completed with exit code 1.
quickstart-compose-validation
The following actions uses node12 which is deprecated and will be forced to run on node16: chrisdickinson/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (./gradlew :datahub-frontend:build :datahub-web-react:build --parallel, UTC)
No files were found with the provided path: **/build/reports/tests/test/** **/build/test-results/test/** **/junit.*.xml. No artifacts will be uploaded.
build (./gradlew :datahub-frontend:build :datahub-web-react:build --parallel, America/New_York)
No files were found with the provided path: **/build/reports/tests/test/** **/build/test-results/test/** **/junit.*.xml. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size
Event File Expired
30.6 KB
Test Results (build) Expired
1.29 MB