Uh oh!
There was an error while loading. Please reload this page.
Dockerfile.e2e: pin to debian stretch variant for now - #2013
Closed
thaJeztah wants to merge 1 commit into
Closed
Conversation
thaJeztah
commented
Jul 22, 2019
MemberAuthor
Ok, that didn't make a difference for that test, unfortunately 😞 |
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
codecov-io
commented
Aug 8, 2019
Codecov Report
@@ Coverage Diff @@## master #2013 +/- ##
=======================================
Coverage 56.79% 56.79% =======================================
Files 311 311 Lines 21836 21836 =======================================
Hits 12402 12402 Misses 8519 8519 Partials 915 915 |
thaJeztah
commented
Dec 4, 2019
MemberAuthor
Flaky test was fixed, so I think we should be ok without this |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We saw a change in behaviour for some tests in moby/moby, and also wondering if this is related to flakiness of the
TestSigProxyWithTTYtest; #2009 (comment)https://jenkins.dockerproject.org/job/docker/job/cli/job/PR-2009/11/execution/node/28/log/