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

bradleyfalzon / gopherci / 297 / 1
60%
master: 61%

Build:
Build:
LAST BUILD BRANCH: review-no-approve
DEFAULT BRANCH: master
Ran 07 Aug 2017 03:45AM UTC
Files 18
Run time 0s
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

07 Aug 2017 03:09AM UTC coverage: 59.974%. First build
GOOGLE_APPLICATION_CREDENTIALS=/tmp/gcloud-GopherCI-dev.json

push

travis-ci

bradleyfalzon
Use ulimit to limit the maximum memory a tool can use

Previously any tool running could consume all available RAM
and swap causing availability issues if the offending process
isn't terminated quickly.

This change adds a configuration parameter to limit the amount
of RAM a process can use. If it exceeds this limit, the process
is terminated, but other processes can continue.

Although we have a Filesystem analyser, which can only limit
memory usage via ulimit, the Docker analyser also uses this
mechanism because Docker's own memory limit will terminate the
container, not just the offending process. I.e. the limit cannot
be applied to our exec instance, only when we've created the
container.

We're also required to run the ulimit command each time, because
each tool is executed with a new shell, which won't inherit the
limits put in place by previous commands.

Fixes #106.

938 of 1564 relevant lines covered (59.97%)

2.42 hits per line

Source Files on job 297.1 (GOOGLE_APPLICATION_CREDENTIALS=/tmp/gcloud-GopherCI-dev.json)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 297
  • Travis Job 297.1
  • db57ab59 on github
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