Skip to content

Ginkgo cli is not forwarding sigterm/sigint signals to its child process. #720

@pprasanthi

Description

@pprasanthi

If I use Ginkgo precompiled-tests we get 2 process, where ginkgo will be parent process and tests will be child process.

164 root 0:00 ginkgo tests/tests.test
172 root 0:00 /go/src/cd.splunkdev.com/integration-tests/search/tests/tests.test --test.timeout=24h0m0s --ginkgo.seed=1600482244 --ginkgo.slowSpecThreshold=5.00000
PPID is 164
PID is 172

When kubernetes pod running this ginkgo process is killed. It is not passing the SIGNAL to the child process. So the container is exiting with successful code which is not expected. Because containers exitCode will decide if the process running inside it is success or not, and an incomplete run is not a successful run.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions