Skip to content

optimize to fetch only relevant fields from source data in doc level … #244

optimize to fetch only relevant fields from source data in doc level …

optimize to fetch only relevant fields from source data in doc level … #244

Triggered via push January 25, 2024 01:23
Status Failure
Total duration 2m 47s
Artifacts
Get-CI-Image-Tag  /  Get-CI-Image-Tag
7s
Get-CI-Image-Tag / Get-CI-Image-Tag
Matrix: build-linux
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
Build Alerting with JDK 17 on windows-latest
Process completed with exit code 1.
Build Alerting with JDK 11 on windows-latest
Process completed with exit code 1.
Build Alerting with JDK 21 on windows-latest
The job was canceled because "_17_windows-latest" failed.
Build Alerting with JDK 21 on windows-latest
Process completed with exit code 1.
Build Alerting with JDK 21 on macos-latest
Process completed with exit code 1.
Build Alerting with JDK 17 on macos-latest
The operation was canceled.
Build Alerting with JDK 11 on macos-latest
The operation was canceled.
Build Alerting with JDK 11 on Linux
Process completed with exit code 1.
Build Alerting with JDK 21 on Linux
Process completed with exit code 1.
Build Alerting with JDK 17 on Linux
Process completed with exit code 1.
Build Alerting with JDK 17 on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 11 on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 21 on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 21 on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 17 on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 11 on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 11 on Linux
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 11 on Linux
Docker pull failed with exit code 1, back off 8.76 seconds before retry.
Build Alerting with JDK 21 on Linux
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Alerting with JDK 17 on Linux
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/