40963107193
73%

Ran 29 Oct 2026 10:15PM UTC

Jobs 1

Files 987

Run time 1min

Badge

Embed ▾

Committed 29 Oct 2026 10:05PM UTC coverage: 72.131% (+0.002%) from 72.129%

Build # 40963107193

Build Type

push

github

Committed by

web-flow

Commit Message

Give Chrome launch its own timeout in consent test (#6993)

TestConsentNativeBrowserForm used one 40s context for the headless
Chrome start and for the test steps. In CI, Chrome took about 39.4s to
come up, so the subtests began with almost no time left and failed with
a confusing "context deadline exceeded" on their first DevTools call.

Give the launch (DevToolsActivePort wait and browser websocket dial) a
separate 60s budget, and start the 40s step budget once the browser is
connected. Also make the next slow start diagnosable: fail at once if
Chrome exits early, write Chrome's stderr to a file and include its tail
in launch failures, and log how long each launch phase took.

Fixes #6992

Co-authored-by: Mecatl <noreply@mecatl.dev>

Coverage Stats

90978 of 126129 relevant lines covered (72.13%)

130.97 hits per line

Coverage Regressions

Lines	Coverage	∆	File
1	81.58	-0.12%	pkg/vmcp/composer/workflow_engine.go

Jobs

ID	Job ID	Ran	Files	Coverage
1	40963107193.1	29 Oct 2026 10:15PM UTC	987	72.13	GitHub Action Run

stacklok / toolhive / 40963107193
73%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 40963107193

stacklok / toolhive / 40963107193 73%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 40963107193

stacklok / toolhive / 40963107193
73%

README BADGES
x