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

cilium / cilium / 40787 / 1
39%
master: 39%

Build:
DEFAULT BRANCH: master
Ran 22 Apr 2022 12:49AM UTC
Files 932
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

21 Apr 2022 08:51PM UTC coverage: 34.183% (-0.02%) from 34.204%
40787.1

push

travis-ci-com

aanm
vagrant: Don't recreate natnetworks

We are hitting issues with the natnetwork creations, both in CI and in
the dev. VM setup. In both cases, it fails to create because the
natnetwork apparently already exists. For the dev. VM, that happens
because the removal of natnetworks sometimes fail, maybe because it's
still in use while being removed. For the CI, it's unclear why it fails
as a previous listing of natnetworks shows nothing.

In any case, one way to work around this is to avoid recreating the
natnetworks each time the VMs are booted. Instead, we can create only
the natnetworks we need and delete the rest. If the creations fail, we
assume it's because they already exist and ignore the failure.

To be able to ignore the creation failures, we must move them outside of
the Vagrant interface configuration and into a proper Shell script,
which we run in a pre-provisioning step.

Signed-off-by: Paul Chaignon <paul@cilium.io>

46826 of 136986 relevant lines covered (34.18%)

2093.97 hits per line

Source Files on job 40787.1
  • Tree
  • List 0
  • Changed 107
  • Source Changed 0
  • Coverage Changed 107
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 27379
  • Travis Job 40787.1
  • ef22668f on github
  • Prev Job for on master (#40727.1)
  • Next Job for on master (#40798.1)
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