Description
The CRI Integration Test logs for the TestRuntimeHandler test are logging empty strings.
Steps to reproduce the issue:
- Run the TestRuntimeHandler apart of the CRI integration tests
- Check the output logs
Describe the results you received:
=== RUN TestRuntimeHandler
runtime_handler_test.go:30: Create a sandbox
runtime_handler_test.go:32: the --runtime-handler flag value is:
runtime_handler_test.go:41: Verify runtimeService.PodSandboxStatus sets RuntimeHandler
runtime_handler_test.go:44: runtimeService.PodSandboxStatus sets RuntimeHandler to
runtime_handler_test.go:47: Verify runtimeService.ListPodSandbox sets RuntimeHandler
runtime_handler_test.go:50: runtimeService.ListPodSandbox sets RuntimeHandler to
Describe the results you expected:
=== RUN TestRuntimeHandler
runtime_handler_test.go:30: Create a sandbox
runtime_handler_test.go:32: the --runtime-handler flag value is: <runtime here>
runtime_handler_test.go:41: Verify runtimeService.PodSandboxStatus sets RuntimeHandler
runtime_handler_test.go:44: runtimeService.PodSandboxStatus sets RuntimeHandler to <runtime here>
runtime_handler_test.go:47: Verify runtimeService.ListPodSandbox sets RuntimeHandler
runtime_handler_test.go:50: runtimeService.ListPodSandbox sets RuntimeHandler to <runtime here>
Output of containerd --version:
containerd containerd.io 1.4.3 269548fa27e0089a8b8278fc4fc781d7f65a939b
Any other relevant information:
N/A
Description
The CRI Integration Test logs for the
TestRuntimeHandlertest are logging empty strings.Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of
containerd --version:Any other relevant information:
N/A