Make the missing-FORGEJO_TOKEN CLI test deterministic #1071

New issue

Open

opened 2026-10-17 02:24:03 +00:00 by jared · 0 comments

jared commented

2026-10-17 02:24:03 +00:00

Owner

Problem

test_a_missing_token_without_a_client_exits_non_zero_naming_forgejo_token (plugins/os-backlog/tests/forgejo_cli_test.rb:72) fails at random. It failed 1 of 5 suite runs on main 55a1ef76 on 2026-10-16, and once in an agent run the same day. The failing run got HTTP 404: GetUserByName instead of a message that names FORGEJO_TOKEN. The test passes no fake client, so a run can reach a real Forgejo lookup instead of the missing-token path. A gate test that fails at random blocks merges.

Reproduce

ruby plugins/os-backlog/tests/all.rb

Run the command five times. Expect one failure at plugins/os-backlog/tests/forgejo_cli_test.rb:72.

Origin

Trigger: suite runs on main 55a1ef76 on 2026-10-16 (1 of 5 failed) and an agent run the same day
Improvised this session: none
Chain: intermittent failure with HTTP 404: GetUserByName ← the test passes no fake client, so a run can reach a real Forgejo lookup ← DESIGN: plugins/os-backlog/tests/forgejo_cli_test.rb:72
Root candidate: none known
Where: plugins/os-backlog/tests/forgejo_cli_test.rb:72
Session: 2baa3b32-f47b-4c8b-9cdd-6270831fe640
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/2baa3b32-f47b-4c8b-9cdd-6270831fe640.jsonl

VERDICT: CREATE — real flake seen 2026-10-16; the test reaches a real lookup without a fake client; parent #835 is user-filed.

## Problem `test_a_missing_token_without_a_client_exits_non_zero_naming_forgejo_token` (plugins/os-backlog/tests/forgejo_cli_test.rb:72) fails at random. It failed 1 of 5 suite runs on main 55a1ef76 on 2026-10-16, and once in an agent run the same day. The failing run got `HTTP 404: GetUserByName` instead of a message that names FORGEJO_TOKEN. The test passes no fake client, so a run can reach a real Forgejo lookup instead of the missing-token path. A gate test that fails at random blocks merges. ## Reproduce ``` ruby plugins/os-backlog/tests/all.rb ``` Run the command five times. Expect one failure at plugins/os-backlog/tests/forgejo_cli_test.rb:72. ## Origin - Trigger: suite runs on main 55a1ef76 on 2026-10-16 (1 of 5 failed) and an agent run the same day - Improvised this session: none - Chain: intermittent failure with `HTTP 404: GetUserByName` ← the test passes no fake client, so a run can reach a real Forgejo lookup ← DESIGN: plugins/os-backlog/tests/forgejo_cli_test.rb:72 - Root candidate: none known - Where: plugins/os-backlog/tests/forgejo_cli_test.rb:72 - Session: 2baa3b32-f47b-4c8b-9cdd-6270831fe640 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os/2baa3b32-f47b-4c8b-9cdd-6270831fe640.jsonl VERDICT: CREATE — real flake seen 2026-10-16; the test reaches a real lookup without a fake client; parent #835 is user-filed.

jared added the

plugin/os-backlog

filed-by/agent

category/code-change

labels

2026-10-17 02:24:03 +00:00

jared referenced this issue

2026-11-12 21:33:59 +00:00

os-backlog tests run with the real FORGEJO_TOKEN and GITHUB_TOKEN #1728