temporalio / temporalio/cli

[Bug] context deadline exceeded in integration tests

Open
#847 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug tests
Dominant language
Go
Stars
379
Forks
103
Avg merge
2d 11h
Merged PRs (30d)
23

Description

Describe the bug

I've created an integration test for Temporal for NixOS over at: https://github.com/NixOS/nixpkgs/blob/master/nixos/tests/temporal.nix

This creates a fresh Temporal server in a VM, and then in the testScript section uses the cli to query that server about cluster status and workflows.

For some reason, the CLI calls will randomly fail with, whilst succeeding with a simple reattempt:

waiting for success: temporal workflow list --output json
... level=ERROR msg="failed reaching server: context deadline exceeded"

I've also tried setting --connect-timeout 120s, and it happens with that too.

This has also been encountered in NixOS's CI system: https://hydra.nixos.org/build/306058770/log

Minimal Reproduction
  1. Install Nix
  2. git clone https://github.com/NixOS/nixpkgs # Large download
  3. cd nixpkgs; nix-build -A nixosTests.temporal --check
Environment/Versions
  • OS and processor: Linux
  • Temporal Version: [e.g. 1.14.0?] and/or SDK version: 1.28.1
  • Are you using Docker or Kubernetes or building Temporal from source? Source

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with nixos/tests/temporal.nix and its testScript, then reproduce the failure with nix-build -A nixosTests.temporal --check. Investigate the temporal workflow list --output json and cluster-status CLI calls against the fresh VM server, using the linked Hydra log for comparison. Done means the integration test no longer intermittently fails with context deadline exceeded.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.