docker / docker/cli

Flaky test: TestPluginSocketCommunication

Open
#6,004 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/testing kind/bug
Dominant language
Go
Stars
6.1k
Forks
2.2k
Avg merge
1d 15h
Merged PRs (30d)
43

Description

Description
=== Failed
=== FAIL: e2e/cli-plugins TestPluginSocketCommunication/detached/the_main_CLI_exits_after_3_signals (1.11s)
    socket_test.go:238: assertion failed: 255 (int) != 1 (int)
    socket_test.go:243: assertion failed: 
        --- ←
        +++ →
        @@ -1 +1,2 @@
        +got 3 SIGTERM/SIGINTs, forcefully exiting

Contributor guide

Open the contributing guide

First steps

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

Research direction

Start by running the e2e/cli-plugins TestPluginSocketCommunication case and inspect socket_test.go around lines 238 and 243. Determine why the detached case reports exit status 255 and the three-signal message instead of the expected result; done means the test is reliable and its assertions pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.