Conversation
|
Are any of those cherry picks not from 1.4? On Fri, Oct 28, 2016 at 10:28 AM, Maciej Szulik notifications@github.com
|
|
[test] |
Nope, just 1.4 branch. |
|
Just out of curiosity, does anything break if we just updated the godep ref? It seems like we're applying a wand here. Also, a +1 on the etcd3 changes those are fixes to issues we had upstream. |
|
I did a patch rebase but it was failing upstream e2e and is too risky right now. We have to rebase 90 patches upstream right now in order to pick a new bump (which if this had been started two weeks ago would have been the right choice). |
|
/cc @mffiedler |
|
This needs to pull in kubernetes/kubernetes#33806 to fix #11199 |
|
@derekwaynecarr I've cherry picked that, but it was a bit tricky, mind having a look if that's ok? |
|
@soltysh did you talk to @PI-Victor about that? those changes are important. |
ddf513b to
64a133a
Compare
|
@bparees yes, if there's a requirement to have those changes in, we need to create a branch and have a official commit that is reachable. |
|
@derekwaynecarr I had to split the cadvisor cherry-pick into two, one is the bump and the other is that cherry-pick itself. (the commit checker was complaining otherwise). |
|
I thought we stated that it was rather late to be pulling in 34000? |
Haven't heard about it, but if you say so it can be easily dropped. |
64a133a to
a802ca1
Compare
|
I dropped 34000, updated client-go to latest 1.4 and updated generated clientset. Hopefully that should be good. |
|
@derekwaynecarr on it |
|
@derekwaynecarr I confirmed this does fix #11199 |
…en writing to audit
…ached multiple times
a802ca1 to
f7027fd
Compare
|
Rebased against latest master and fixed the errors that showed up in tests. |
|
Evaluated for origin test up to f7027fd |
|
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10898/) (Base Commit: 63642d6) |
|
Is this being tracking in a bugzilla for OCP anywhere? |
|
Tests are panicking
|
|
I'll start looking into the panics. |
|
The panic is because our vendored copies of |
|
ETA on fixes? This is blocking a bunch of stuff. |
|
Working on it |
|
This is why the former struct has Timeout and the latter doesn't: #11104 |
|
Testing a fix in #11709 |
|
Moving to #11709 |
Resovles #11565.
@liggitt @smarterclayton ptal
@pweil- @mfojtik fyi
The summary (master #PR: title (cherry-pick #PR) - why):
able to modify that
34000: Set deserialization cache size based on target memory usage (34213) - To reduce memory usage to reasonable levels in smaller clustersNot sure about: