make cgroup imports linux-only

[liggitt]

cgroups.ParseCgroupFile is only available on linux

fixes #14718

[liggitt]

[test]

[liggitt]

@bparees PTAL

[bparees]

lgtm
[testextended][extended:core(build with a quota)]

[bparees]

guess it's time to add cross-compiling checks to the merge queue? :(

[liggitt]

guess it's time to add cross-compiling checks to the merge queue? :(

eh, it's rare and easy to fix when it happens

[openshift-bot]

Evaluated for origin testextended up to f3cc20b

[openshift-bot]

continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_extended/644/) (Base Commit: 8c017d2) (PR Branch Commit: f3cc20b) (Extended Tests: core(build with a quota))

[liggitt]

[merge][severity:bug]

[openshift-bot]

continuous-integration/openshift-jenkins/merge Waiting: You are in the build queue at position: 5

[openshift-bot]

Evaluated for origin merge up to f3cc20b

[bparees]

7 hours for a test job to fail. Wheee. Ben Parees | OpenShift

…

On Jun 17, 2017 06:07, "OpenShift Bot" ***@***.***> wrote: continuous-integration/openshift-jenkins/test FAILURE ( https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2350/) (Base Commit: 8c017d2 <8c017d2>) (PR Branch Commit: f3cc20b <f3cc20b> ) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14717 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEvl3p1QdgYkc7FM0MxsVAk1hkAAFiEGks5sE6VxgaJpZM4N9G8V> .

[bparees]

in case anyone wants to investigate why the test took 6 hours, job was here:
https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin_integration/3355/

[test]

[bparees]

So up to the integration test stage, things should have only taken maybe an hour.

Within the integration test stage, I see no successful test taking longer than 84s (and most of them are sub 1s), meaning I don't see any individual tests that appeared to get "stuck" but ultimately pass after consuming a bunch of time.

And then at the end of the stage we just fail:

There was no error output from the command.
Running test/end-to-end/core.sh:387: executing 'oc delete pod cli-with-token' expecting success...
SUCCESS after 0.257s: test/end-to-end/core.sh:387: executing 'oc delete pod cli-with-token' expecting success
Standard output from the command:
pod "cli-with-token" deleted

There was no error output from the command.
Connection to 172.18.7.30 closed by remote host.
++ export status=FAILURE
++ status=FAILURE
+ set +o xtrace
########## FINISHED STAGE: FAILURE: RUN INTEGRATION TESTS [06h 06m 30s] ##########

I don't know what that next command was that failed/hung or why.

[openshift-bot]

Evaluated for origin test up to f3cc20b

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2353/) (Base Commit: f12892b) (PR Branch Commit: f3cc20b)