Skip to content

feat: adding cache functionality in Receiver for unsorted datapoints #14

feat: adding cache functionality in Receiver for unsorted datapoints

feat: adding cache functionality in Receiver for unsorted datapoints #14

Triggered via pull request August 14, 2024 13:39
Status Failure
Total duration 1m 42s
Artifacts

tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
unit
Process completed with exit code 3.
e2e
Process completed with exit code 1.
unit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-node@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
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
e2e
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
e2e
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/