tilt ci waits on a local job yaml, but fails to wait for a helm installed job

Open
#6,315 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, helm, kubernetes
Domain
ci-cd, devops, testing-qa

Research direction

Reproduce the behavior with the linked tilt-job-example repository by running tilt ci and comparing the local YAML job with the Helm-installed job. Start at the tilt ci workload-waiting path and trace how each job is detected as complete. Done means tilt ci waits for both jobs and the longer-running cukes job reports completion before exit.

Written by the indexing model from the issue text.

Description

bug
Expected Behavior

I would expect both jobs to finish before tilt ci exits

Current Behavior

Only the non-helm installed job finished before tilt ci exits

        cukes │ Serving files on port 8000
        cukes │ Sleeping for 80 seconds
 example-html │ Done sleeping
 example-html │      ┊ Scheduled       - <1s
 example-html │      ┊ Initialized     - <1s
 example-html │      ┊ Completed       - 12s
SUCCESS. All workloads are healthy.
Steps to Reproduce
  1. Repo to reproduce this issue: https://github.com/adamdavis40208/tilt-job-example
  2. tilt ci
  3. Notice the longer running job "cukes" doesn't print that it's done before tilt ci exits.
Context
tilt doctor Output
Tilt: v0.33.10, built 2023-12-15
System: darwin-arm64
---
Docker
- Host: unix:///Users/r625040/.docker/run/docker.sock
- Server Version: 24.0.7
- API Version: 1.43
- Builder: 2
- Compose Version: v2.23.3-desktop.2
---
Kubernetes
- Env: kind
- Context: kind-stack-evaluation-orchestrator-agent
- Cluster Name: kind-stack-evaluation-orchestrator-agent
- Namespace: default
- Container Runtime: containerd
- Version: v1.28.6
- Cluster Local Registry: none
---
About Your Use Case

With tilt ci not waiting for jobs (how we run integration tests), we're a bit broken running our E2E integration tests

Dominant language
Go
Stars
10.1k
Forks
413
Avg merge
1d 10h
Merged PRs (30d)
6

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.

More from tilt-dev/tilt

All issues in tilt-dev/tilt

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.