Skip to content

Commit

Permalink
ci: Attempt to diagnose Trino failures
Browse files Browse the repository at this point in the history
  • Loading branch information
emk committed Feb 29, 2024
1 parent 05b9e53 commit efa71f3
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
4 changes: 3 additions & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ jobs:
just docker-run-trino
just check-trino
docker tag trino-joinery ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:latest
- name: Show docker logs
if: failure()
run: docker logs trino-joinery
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
Expand Down
1 change: 1 addition & 0 deletions src/drivers/trino/mod.rs
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,7 @@ macro_rules! retry_trino_error {
match $e {
Ok(val) => break Ok(val),
Err(e) if should_retry(&e) && max_tries > 0 => {
eprintln!("Retrying Trino query after error");
sleep(sleep_duration).await;
max_tries -= 1;
sleep_duration *= 2;
Expand Down

0 comments on commit efa71f3

Please sign in to comment.