-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Post-rebase: conformance test hung getting logs off the node #12458
Comments
This is probably the hanging VM problem I saw in a few CI runs. The console
listed multiple docker soft lockups. Not sure what's going on.
…On Wed, Jan 11, 2017 at 10:41 PM Clayton Coleman ***@***.***> wrote:
@ncdc <https://github.com/ncdc>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12458 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAABYu21lwJERBrG2klluAxyMGeeaBn1ks5rRaDOgaJpZM4LhVwG>
.
|
I'm going to disable memcfg notifications until this is fixed. |
Except we don't have the flag yet until we pick up 1.5.2 |
There is a disable patch, @soltysh on your PR you'll want to ignore that but you may need to default the flag to off in master. |
Why'd you reopen? |
@smarterclayton I've added test for |
Just reopened so we have a place to track turning it to a flag. I think we still want this in 3.5 if we can get the soft lock fixed - I'm hoping to get enough testing that we can turn it back on before thatz |
AFAIK the lockup is still an issue. The kube 1.6 rebase adds the |
Lowering priority for now to get this off the blocker list |
@derekwaynecarr @sjenning this is the origin issue for the memcg kernel issue. Feel free to close if you just want to manage this in the bz linked above. |
Yeah, this might be drawn out. We can just open a PR to enable it when the kernel BZ is fixed. Or when we decide to disable THPs on origin 🤞 |
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/10037/console
This is unusual - I wonder if we ran out of disk space. Opening to have something to track.
The text was updated successfully, but these errors were encountered: