Skip to content

chore(logging): remove redis-progress-markers feature flag #20358

chore(logging): remove redis-progress-markers feature flag

chore(logging): remove redis-progress-markers feature flag #20358

Triggered via pull request June 30, 2026 16:24
Status Failure
Total duration 2m 31s
Artifacts

ci.yml

on: pull_request
Detect Version
Detect Version
Test and Build  /  Test and Build
2m 19s
Test and Build / Test and Build
Migrate Dev DB  /  Apply Database Migrations
Migrate Dev DB / Apply Database Migrations
Check Docs Changes
Check Docs Changes
Matrix: Build ARM64 (GHCR Only)
Migrate DB  /  Apply Database Migrations
Migrate DB / Apply Database Migrations
Matrix: Build Dev ECR
Matrix: Build AMD64
Matrix: Create GHCR Manifests
Process Docs  /  Process Documentation Embeddings
Process Docs / Process Documentation Embeddings
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 6 warnings
Test and Build / Test and Build
Process completed with exit code 1.
lib/logs/execution/logging-session.test.ts > LoggingSession progress-marker write path > tells completion to read Redis markers only when the flag is on (no wasted ops when off): apps/sim/lib/logs/execution/logging-session.test.ts#L793
AssertionError: expected last "vi.fn()" call to have been called with [ ObjectContaining{…} ] - Expected + Received [ { + "completionFailure": undefined, + "costSummary": { + "baseExecutionCharge": 0, + "models": {}, + "totalCompletionTokens": 0, + "totalCost": 0, + "totalInputCost": 0, + "totalOutputCost": 0, + "totalPromptTokens": 0, + "totalTokens": 0, + }, + "endedAt": "2026-06-30T16:25:33.358Z", "executionId": "exec-off", - "readProgressMarkers": false, + "executionState": undefined, + "finalOutput": { + "ok": true, + }, + "finalizationPath": "completed", + "isResume": false, + "level": undefined, + "readProgressMarkers": true, + "status": undefined, + "totalDurationMs": 0, + "traceSpans": [], + "workflowInput": undefined, }, ] ❯ lib/logs/execution/logging-session.test.ts:793:43
lib/logs/execution/logging-session.test.ts > LoggingSession progress-marker write path > falls back to the SQL path when flag resolution throws: apps/sim/lib/logs/execution/logging-session.test.ts#L775
AssertionError: expected "vi.fn()" to not be called at all, but actually been called 1 times Received: 1st vi.fn() call: Array [ "exec-fallback", Object { "blockId": "b1", "blockName": "Fetch", "blockType": "api", "startedAt": "2026-06-27T10:00:00.000Z", }, ] Number of calls: 1 ❯ lib/logs/execution/logging-session.test.ts:775:41
lib/logs/execution/logging-session.test.ts > LoggingSession progress-marker write path > writes markers via jsonb_set UPDATE when the flag is off: apps/sim/lib/logs/execution/logging-session.test.ts#L764
AssertionError: expected "vi.fn()" to not be called at all, but actually been called 1 times Received: 1st vi.fn() call: Array [ "exec-sql", Object { "blockId": "b1", "blockName": "Fetch", "blockType": "api", "startedAt": "2026-06-27T10:00:00.000Z", }, ] Number of calls: 1 ❯ lib/logs/execution/logging-session.test.ts:764:41
Test and Build / Test and Build
sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (1)
Test and Build / Test and Build
Process completed with exit code 1.
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps