Skip to content
Ziggurat CI

adds max-poll-interval-ms to consumer config #867

Sign in to view logs

adds max-poll-interval-ms to consumer config

adds max-poll-interval-ms to consumer config #867

Triggered via pull request August 24, 2023 11:12
@shubhang93shubhang93
synchronize #274
support-max-poll-interval-ms
Status Success
Total duration 10m 8s
Artifacts –

build.yml

on: pull_request
lint_check
1m 18s
lint_check
run_tests_with_kafka_cluster
9m 58s
run_tests_with_kafka_cluster
calculate_coverage
6m 34s
calculate_coverage
deploy_to_clojars
0s
deploy_to_clojars
send_update_event
0s
send_update_event
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
lint_check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/
calculate_coverage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/
run_tests_with_kafka_cluster
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, 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/