-
Notifications
You must be signed in to change notification settings - Fork 42k
Closed
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/cliCategorizes an issue or PR as relevant to SIG CLI.Categorizes an issue or PR as relevant to SIG CLI.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.
Description
Which jobs are failing:
pull-kubernetes-integration
Which test(s) are failing:
run_kubectl_diff_tests
Since when has it been failing:
https://prow.k8s.io/?job=pull-kubernetes-integration&state=failure It only shows failure cases in recent 2 days.
The last date is Apr 10 16:04:18Apr 10 2021, 16:04:18 UTC+0800
Testgrid link:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/101013/pull-kubernetes-integration/1381512796969111552
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/101006/pull-kubernetes-integration/1381460511371038720
Reason for failure:
�(B�[mdiff -u -N /tmp/LIVE-706114995/v1.Pod.namespace-1618192119-8332.test-pod /tmp/MERGED-419169654/v1.Pod.namespace-1618192119-8332.test-pod
--- /tmp/LIVE-706114995/v1.Pod.namespace-1618192119-8332.test-pod 2021-04-12 01:48:42.133356843 +0000
+++ /tmp/MERGED-419169654/v1.Pod.namespace-1618192119-8332.test-pod 2021-04-12 01:48:42.137357267 +0000
@@ -19,7 +19,7 @@
f:name: {}
manager: kubectl
operation: Apply
- time: "2021-04-12T01:48:41Z"
+ time: "2021-04-12T01:48:42Z"
name: test-pod
namespace: namespace-1618192119-8332
resourceVersion: "1026"
!!! [0412 01:48:42] Call tree:
!!! [0412 01:48:42] 1: /home/prow/go/src/k8s.io/kubernetes/test/cmd/../../third_party/forked/shell2junit/sh2ju.sh:47 run_kubectl_diff_tests(...)
!!! [0412 01:48:42] 2: /home/prow/go/src/k8s.io/kubernetes/test/cmd/../../third_party/forked/shell2junit/sh2ju.sh:112 eVal(...)
!!! [0412 01:48:42] 3: /home/prow/go/src/k8s.io/kubernetes/test/cmd/legacy-script.sh:132 juLog(...)
!!! [0412 01:48:42] 4: /home/prow/go/src/k8s.io/kubernetes/test/cmd/legacy-script.sh:533 record_command(...)
!!! [0412 01:48:42] 5: hack/make-rules/test-cmd.sh:191 runTests(...)
+++ exit code: 1
Anything else we need to know:
while true
do
kubectl delete pod/test-pod && kubectl apply --server-side -f hack/testdata/pod.yaml; kubectl diff --server-side -f hack/testdata/pod.yaml; echo $?
sleep 1
done
I tried to reproduce it locally, but can't
Metadata
Metadata
Assignees
Labels
kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.Categorizes issue or PR as related to a consistently or frequently failing test.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/cliCategorizes an issue or PR as relevant to SIG CLI.Categorizes an issue or PR as relevant to SIG CLI.triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.