docker-py: skip flaky AttachContainerTest::test_attach_no_stream (again)#40500
docker-py: skip flaky AttachContainerTest::test_attach_no_stream (again)#40500cpuguy83 merged 1 commit intomoby:masterfrom
Conversation
3585755 to
32ab61c
Compare
|
Interesting; it's now complaining about other gofmt issues; I thought I rebased, but let me try again |
|
@thaJeztah those goimports errors were not covered in https://github.com/moby/moby/pull/40501/files . Curious, are we linting a random set of |
|
That's what I'm curious about as well. I know golangci-lint has a configurable limit of warnings per type of linting, but that wouldn't explain why it would completely ignore things |
32ab61c to
001820c
Compare
|
CI Failure is unrelated; Windows image failed to be built for unknown reasons (output isn't very useful); |
|
Windows |
|
The windows FROM mcr.microsoft.com/windows/servercore:10.0.17763.1039
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]
RUN Write-Host it works!A |
This test was disabled in the past, but re-enabled when we upgraded docker-py to 4.2.0. The test looks to be still flaky though, so skipping it again: ``` [2020-02-10T23:40:44.429Z] =================================== FAILURES =================================== [2020-02-10T23:40:44.429Z] __________________ AttachContainerTest.test_attach_no_stream ___________________ [2020-02-10T23:40:44.429Z] tests/integration/api_container_test.py:1250: in test_attach_no_stream [2020-02-10T23:40:44.429Z] assert output == 'hello\n'.encode(encoding='ascii') [2020-02-10T23:40:44.429Z] E AssertionError: assert b'' == b'hello\n' [2020-02-10T23:40:44.429Z] E Right contains more items, first extra item: 104 [2020-02-10T23:40:44.429Z] E Use -v to get the full diff [2020-02-10T23:40:44.429Z] ------- generated xml file: /src/bundles/test-docker-py/junit-report.xml ------- ```` Signed-off-by: Sebastiaan van Stijn <[email protected]>
001820c to
da6c142
Compare
relates to docker/docker-py#2513
This test was disabled in the past (#39848), but re-enabled when we upgraded docker-py to 4.2.0 (#40467).
The test looks to be still flaky though, so skipping it again: