Skip to content
check

fix: Adjust tailer loop criteria so it is actually re-tested #5765

Sign in to view logs

fix: Adjust tailer loop criteria so it is actually re-tested

fix: Adjust tailer loop criteria so it is actually re-tested #5765

Triggered via pull request August 16, 2024 11:53
@paul1rpaul1r
opened #13906
paul1r/tailer_loop_adjustment
Status Success
Total duration 5m 43s
Artifacts –

check.yml

on: pull_request
check  /  checkFiles
4m 4s
check / checkFiles
check  /  faillint
3m 24s
check / faillint
check  /  golangciLint
3m 36s
check / golangciLint
check  /  integration
5m 15s
check / integration
check  /  lintFiles
1m 22s
check / lintFiles
check  /  testLambdaPromtail
1m 15s
check / testLambdaPromtail
check  /  testPushPackage
52s
check / testPushPackage
check  /  collectPackages
9s
check / collectPackages
Matrix: check / testPackages
check  /  check
8s
check / check
check  /  failCheck
0s
check / failCheck
Fit to window
Zoom out
Zoom in

Annotations

1 warning
check / golangciLint
The following actions use a deprecated Node.js version and will be forced to run on node20: golangci/golangci-lint-action@08e2f20817b15149a52b5b3ebe7de50aff2ba8c5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/