Change:
"github.com/onsi/ginkgo" ) <del> var _ = SIGDescribe("[Feature:Windows] Cpu Resources", func() { </del> <ins> var _ = SIGDescribe("[Feature:Windows] Cpu Resources [Serial]", func() { </ins> f := framework.NewDefaultFramework("cpu-resources-test-windows") // The Windows 'BusyBox' image is PowerShell plus a collection of scripts and utilities to mimic common busybox commands

Discussion:
Which jobs are failing: Which test(s) are failing: Since when has it been failing: Testgrid link: Reason for failure: Anything else we need to know: /sig windows /cc /priority critical-urgent /milestone v1.18
/assign
I think we might need to run this job in Serial. This test is flakey and fails the same way each time. Looking at the logs for the failures I see we try to start a single pod ï¿½[1mSTEPï¿½[0m: Creating one pod with limit set to '0.5' ï¿½[1mSTEPï¿½[0m: Creating one pod with limit set to '500m' But then events captured in the logs show the pod getting rescheduled to a different node ï¿½[1mSTEPï¿½[0m: Collecting events from namespace "cpu-resources-test-windows-3448". ï¿½[1mSTEPï¿½[0m: Found 8 events. Mar 17 14:08:03.918: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for cpulimittest--30aa-4ac7-9ad2-: {default-scheduler } Scheduled: Successfully assigned cpu-resources-test-windows-3448/cpulimittest--30aa-4ac7-9ad2- to 2861k8s001 Mar 17 14:08:03.918: INFO: At 0001-01-01 00:00:00 +0000 UTC - event for cpulimittest--2fea-4e58-8dc7-: {default-scheduler } Scheduled: Successfully assigned cpu-resources-test-windows-3448/cpulimittest--2fea-4e58-8dc7- to 2861k8s000 Mar 17 14:08:03.918: INFO: At 2020-03-17 14:05:44 +0000 UTC - event for cpulimittest--30aa-4ac7-9ad2-: {kubelet 2861k8s001} Pulled: Container image "e2eteam/busybox:1.29" already present on machine Mar 17 14:08:03.

918: INFO: At 2020-03-17 14:05:44 +0000 UTC - event for cpulimittest--30aa-4ac7-9ad2-: {kubelet 2861k8s001} Created: Created container cpulimittest--30aa-4ac7-9ad2- Mar 17 14:08:03.918: INFO: At 2020-03-17 14:05:46 +0000 UTC - event for cpulimittest--30aa-4ac7-9ad2-: {kubelet 2861k8s001} Started: Started container cpulimittest--30aa-4ac7-9ad2- Mar 17 14:08:03.918: INFO: At 2020-03-17 14:05:56 +0000 UTC - event for cpulimittest--2fea-4e58-8dc7-: {kubelet 2861k8s000} Pulled: Container image "e2eteam/busybox:1.29" already present on machine Mar 17 14:08:03.918: INFO: At 2020-03-17 14:05:56 +0000 UTC - event for cpulimittest--2fea-4e58-8dc7-: {kubelet 2861k8s000} Created: Created container cpulimittest--2fea-4e58-8dc7- Mar 17 14:08:03.918: INFO: At 2020-03-17 14:05:59 +0000 UTC - event for cpulimittest--2fea-4e58-8dc7-: {kubelet 2861k8s000} Started: Started container cpulimittest--2fea-4e58-8dc7- Mar 17 14:08:03.977: INFO: POD NODE PHASE GRACE CONDITIONS Mar 17 14:08:03.

977: INFO: cpulimittest--30aa-4ac7-9ad2- 2861k8s001 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:38 +0000 UTC }] Mar 17 14:08:03.977: INFO: cpulimittest--2fea-4e58-8dc7- 2861k8s000 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:49 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:06:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:06:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-03-17 14:05:49 +0000 UTC }] Mar 17 14:08:03.977: INFO: Mar 17 14:08:04.093: INFO:
/cc
Yes. That's most probably the case. I am preparing a PR for this.
/reopen The job is still red. It seems that was merged in the wrong branch. Can you check? This job runs in branch as well? Do we need to cherry-pick it?
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
Any news?
is the cherry-pick PR to bring the fix/change into 1.18 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