Anthony Sottile

what do you mean "check script"

Hmmm, I'm not seeing where in the README it says that `pip` will install it into `/usr/bin`. Unless you're using your system package manager to install `dumb-init` (such as `apt-get`)...

We've done this in the following way: ```dockerfile CMD ["dumb-init", "./setup.sh"] ``` ```sh #!/usr/bin/env bash # Run some runtime setup code echo hi > /etc/app.conf # exec the application exec...

Would this be run once per box or once per everything (I don't think the second is possible, and the first you'd need to store some state on disk probably?)

here's a sketch for the minimum that's needed: https://github.com/pytest-dev/pytest/issues/5243#issuecomment-491522595 -- I don't believe this is possible in a cross-platform manner, especially on windows

my guess is gitlab is brutally killing the container rather than SIGTERM, or the root of your process tree is not acting as a [proper init system](https://engineeringblog.yelp.com/2016/01/dumb-init-an-init-for-docker.html) and forwarding the...

iirc you can control which signal bazel sends through a test wrapper -- at stripe we used int then term then kill

what I would suggest is document this: https://github.com/pytest-dev/pytest/issues/9142#issuecomment-932623158 and then maybe link a blurb about container init systems (dumb-init has a decent blog post on this) or signal changers (dumb-init...

iirc bazel by default is very aggressive and uses SIGKILL (uncatchable)

teardowns are always associated with the most recent test which ran in some cases this results in multiple statuses for a single test everything shown in the issue is expected