ACP workflow tests time out under CI nextest profile on main

[thewoolleyman]

Summary

Three fabro-cli::it workflow::acp::* tests time out at 120s under the CI nextest profile on clean upstream/main.

This came up while validating PR #552. The same timeouts reproduce on upstream/main without the PR changes, so this appears to be a preexisting master/main issue rather than a regression from that PR.

Reproduction

From a clean detached worktree at upstream/main:

• Commit: 8c7d5dc7d0375fb8e7d1d3f47e7e6639979d8517
• Command:

CARGO_TARGET_DIR=/data/projects/fabro/target cargo nextest run --locked -p fabro-cli --profile ci --no-fail-fast workflow::acp::acp

Result

All three selected ACP tests time out at the CI profile's 120s limit:

TIMEOUT [120.132s] fabro-cli::it workflow::acp::acp_artifacts_are_listed_when_touched_file_mtime_precedes_attempt_start
TIMEOUT [120.168s] fabro-cli::it workflow::acp::acp_backend_does_not_inject_registered_provider_credentials
TIMEOUT [120.171s] fabro-cli::it workflow::acp::acp_backend_workflow

Summary:

3 tests run: 0 passed, 3 timed out, 979 skipped

Expected

The ACP workflow tests should complete within the CI profile timeout, or the CI profile timeout/test behavior should be adjusted if these tests legitimately need more than 120s in this environment.

Notes

The full workspace CI-profile run on PR #552 also reached the same three final timeouts after the rest of the suite passed:

6954 tests run: 6951 passed, 3 timed out, 187 skipped

[swerner]

Thanks for the detailed report @thewoolleyman. It looks like this issue is resolved now - I ran these tests locally on current main and recent PR CI is green as well. Are you able to reproduce this still?