1
63%
master: 64%

Ran 27 Mar 2025 11:29AM UTC

Files 83

Run time 2s

Badge

Embed ▾

Committed 27 Mar 2025 11:27AM UTC coverage: 63.325% (+0.06%) from 63.268%

Job # 14105458481.1

Build Type

Pull #33

github

Committed by

brianneville

Commit Message

containers/docker: set valid maximum timeout for force-stopping container

If the ctx deadline is used as a timeout but the container
does not handle SIGTERM, then by the time SIGKILL is sent,
the ctx will have expired.
To fix this, spend at most half of the ctx deadline waiting
before issuing the SIGKILL.

To ensure that this does not take too long (as the Force
fields intention is to forcibly kill the container), the
timeout is capped at a maximum of 10 seconds (which is the
default timeout used by docker).

Also update the test to make it deterministic.
Previously the test could fail if the time.Now() in
ContainerStop called too late.

Pull Request Pull Request #33: containers/docker: set valid maximum timeout for force-stopping container

Run Details

1611 of 2544 relevant lines covered (63.33%)

0.71 hits per line

openconfig / containerz / 14105458481 / 1
63%
master: 64%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 14105458481.1

openconfig / containerz / 14105458481 / 1 63% master: 64%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 14105458481.1

openconfig / containerz / 14105458481 / 1
63%
master: 64%

README BADGES
x