test: unit test flakes for activity logs stream

Open

#407 opened on Mar 17, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 45/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: go
Domain: cli, testing-qa

Research direction

Start with internal/pkg/platform/activity_test.go around lines 249-269 and run the TestPlatformActivity_StreamingLogs case from the linked Actions failure. Investigate the polling timing behind the mismatch between the expected three Activity calls and the actual four, then verify the test reliably covers the request-failure behavior without flaking.

Written by the indexing model from the issue text.

Description

code health

Summary

A recent test run on main failed for reasons unrelated to the recent commit. Perhaps a timing of a poll?

The retry succeeded! 🧪 ✨

Preview

🔗 https://github.com/slackapi/slack-cli/actions/runs/23178071163/job/67344594805

=== RUN   TestPlatformActivity_StreamingLogs/should_return_nil_if_TailArg_is_set_and_activity_request_fails_while_polling
    activity_test.go:267: 
        	Error Trace:	/Users/runner/work/slack-cli/slack-cli/internal/pkg/platform/activity_test.go:267
        	            				/Users/runner/work/slack-cli/slack-cli/internal/pkg/platform/activity_test.go:296
        	Error:      	Not equal: 
        	            	expected: 3
        	            	actual  : 4
        	Test:       	TestPlatformActivity_StreamingLogs/should_return_nil_if_TailArg_is_set_and_activity_request_fails_while_polling
        	Messages:   	Expected number of calls (3) of method Activity does not match the actual number of calls (4).

https://github.com/slackapi/slack-cli/blob/f23e6d3546f93e8fba8f384f89c3b77dacb34934/internal/pkg/platform/activity_test.go#L249-L269

Dominant language: Go
Stars: 305
Forks: 46
Avg merge: 1d 11h
Merged PRs (30d): 23

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

ci: macOS contributor nightly fails to build aws-lc-fips-sys (Could not find Go) Open

bug github_actions

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

registrystack/registry-stack#1393 · Opened Sep 24, 2026
self-host checker: `write` with the wrong argument count is not E004 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

JakeChampion/lang#10213 · Opened Sep 24, 2026
Bump protobufjs to >=7.5.5 to address GHSAs (transitive via @oasisprotocol/client) Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

oasisprotocol/oasis-sdk#2523 · Opened Sep 24, 2026
x/vulndb: suggestion regarding GO-2026-6452 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

golang/vulndb#6587 · Opened Sep 24, 2026
authentik_source_oauth: access_token_url/authorization_url/oidc_jwks_url/profile_url cause a permanent diff when oidc_well_known_url is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

goauthentik/terraform-provider-authentik#981 · Opened Sep 24, 2026

More Go issues