-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Closed
Labels
area/testingkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.platform/windowsstatus/needs-attentionCalls for a collective discussion during a review sessionCalls for a collective discussion during a review session
Description
Seen on #39569 (comment)
RS5 failed due to #39574, but integration tests are not marked as "failed"
https://jenkins.dockerproject.org/job/Docker-PRs-WoW-RS5-Process/3055/console
09:13:44 Running C:\gopath\src\github.com\docker\docker\integration\container
09:13:45 INFO: Windows Base image is microsoft/windowsservercore
09:13:45 INFO: Testing against a local daemon
...
09:13:52 === RUN TestHealthKillContainer
09:13:59 --- FAIL: TestHealthKillContainer (7.58s)
09:13:59 health_test.go:57: assertion failed: error is not nil: Error response from daemon: Invalid signal: SIGUSR1
...
09:16:21 FAIL
09:16:21 Running C:\gopath\src\github.com\docker\docker\integration\image
Then it continues with test-integration-cli
10:22:01 OK: 524 passed, 548 skipped
10:22:01 PASS
10:22:01 ok github.com/docker/docker/integration-cli 3921.066s
10:22:02 INFO: Integration tests ended at 07/19/2019 10:22:02. Duration:01:05:31.5617086
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/testingkind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.platform/windowsstatus/needs-attentionCalls for a collective discussion during a review sessionCalls for a collective discussion during a review session