mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-01-30 05:52:15 +00:00
tests: k8s: parallel: Increase timeout
We've seen a few cases where we fail the test due to timeout and when we
print the pods we just see that they've been created.
With that in mind, let's just increase the timeout a little bit.
Example:
```
not ok 1 Parallel jobs in 6250ms
(in test file k8s-parallel.bats, line 41)
`kubectl wait --for=condition=Ready --timeout=$timeout pod -l jobgroup=${job_name}' failed
No resources found in kata-containers-k8s-tests namespace.
[bats-exec-test:71] INFO: k8s configured to use runtimeclass
job.batch/process-item-test1 created
job.batch/process-item-test2 created
job.batch/process-item-test3 created
NAME STATUS COMPLETIONS DURATION AGE
process-item-test1 Running 0/1 0s
process-item-test2 Running 0/1 0s
process-item-test3 Running 0/1 0s
error: no matching resources found
No resources found in kata-containers-k8s-tests namespace.
No resources found in kata-containers-k8s-tests namespace.
DEBUG: system logs of node 'aks-nodepool1-25989463-vmss000000' since test start time (2025-11-01 16:39:03)
-- No entries --
job.batch "process-item-test1" deleted
job.batch "process-item-test2" deleted
job.batch "process-item-test3" deleted
```
Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
This commit is contained in:
@@ -38,7 +38,7 @@ setup() {
|
||||
kubectl get jobs -l jobgroup=${job_name}
|
||||
|
||||
# Check the pods
|
||||
kubectl wait --for=condition=Ready --timeout=$timeout pod -l jobgroup=${job_name}
|
||||
kubectl wait --for=condition=Ready --timeout=120s pod -l jobgroup=${job_name}
|
||||
|
||||
# Check output of the jobs
|
||||
for i in $(kubectl get pods -l jobgroup=${job_name} -o name); do
|
||||
|
||||
Reference in New Issue
Block a user