Change:
}, { "ImportPath": "github.com/go-openapi/jsonpointer", <del> "Comment": "v0.18.0", </del> <ins> "Comment": "v0.19.0", </ins> "Rev": "ef5f0afec364d3b9396b7b77b43dbe26bf1f8004" }, { "ImportPath": "github.com/go-openapi/jsonreference", <del> "Comment": "v0.18.0", </del> <ins> "Comment": "v0.19.0", </ins> "Rev": "8483a886a90412cd6858df4ea3483dce9c8e35a3" }, {

Discussion:
<!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs --Which jobs are failing: Which test(s) are failing: Since when has it been failing: Test has been failing since 3/24, at 9:19 Testgrid link: Reason for failure: Error during : Due to release v0.19.0 of and the morning of 3/23. /milestone v1.14 /kind failing-test /priority critical-urgent /cc
Adding sig-testing until someone claims it /sig testing
The file specifies both a version and a SHA commit. For the hash is the same for releases v0.17.0 through v0.19.0. The same goes for . The hash has been the same for releases v0.17.0 through v0.19.0. For both of these packages, the change from v0.18.0 (whats in ) to v0.19.0 seems to be the addition of a and files.
I think this is the presubmit job that corresponds to (which i'm hoping will be a valid solution) So just waiting to see if it works (runtime about an hour)
Forgot to mention that this also needs to be fixed in master applies the fix directly to 1.14 branch applies the fix to master
Thanks for monitoring it so closely and for preparing the fixes I think and a cherry-pick to the branch make sense. I'd rather hold onto merging them until after we've released later today (), especially for 1.14. My reasoning is that we've seen the tests stable with v0.18 of both dependencies for quite a while. Even if the changes are small, it might still be worth letting the CI run for a while if we update any dependencies. Because the job is very quick, I feel we can still decide to go for it later today if we decide otherwise; I'll hold back for now and let's speak at today's release meeting.
Hm, looking at it a bit more, there's no real change between the 2 releases: <img width="308" alt="Screen Shot 2019-03-25 at 10 37 11" src="https://user-"A of seems to have triggered the new releases, but none of the 2 dependencies seem to vendor it (directly or indirectly).

I'm happy with that going in, at least for . Let's still chat in a few hours about how to proceed.
godeps adds comments that correspond to the latest tag for the referenced sha. that means a new tag on the same sha broke our CI verification, so we need to update the generated Godep file to pick up the new comments. there are no code or content changes associated (since the SHA we're using is not changing), and the contents of will not change.
This is affecting all PR's against master as well:
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Repurposing this as umbrella issue for the godeps issue since it's affecting multiple branches
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details