• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

openconfig / containerz / 14105458481
63%
master: 64%

Build:
Build:
LAST BUILD BRANCH: 20260204-mdev-close-writer
DEFAULT BRANCH: master
Ran 27 Mar 2025 11:29AM UTC
Jobs 1
Files 83
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

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

Pull #33

github

brianneville
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 #33: containers/docker: set valid maximum timeout for force-stopping container

5 of 5 new or added lines in 1 file covered. (100.0%)

1611 of 2544 relevant lines covered (63.33%)

0.71 hits per line

Jobs
ID Job ID Ran Files Coverage
1 14105458481.1 27 Mar 2025 11:29AM UTC 83
63.33
GitHub Action Run
Source Files on build 14105458481
  • Tree
  • List 83
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #33
  • PR Base - master (#14095964032)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc