juju test suite should be isolated and do 0 outbound network requests
Bug #1233601 reported by
William Reade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Ian Booth |
Bug Description
http://
Well, I see how, but not how the code landed like that. Skipping them for now.
Related branches
lp:~wallyworld/juju-core/turn-on-network-isolation
- Juju Engineering: Pending requested
-
Diff: 1395 lines (+216/-249)32 files modifiedenvirons/jujutest/livetests.go (+0/-14)
environs/jujutest/tests.go (+0/-4)
provider/azure/azure_test.go (+6/-6)
provider/azure/config_test.go (+1/-2)
provider/azure/customdata_test.go (+1/-2)
provider/azure/instance_test.go (+2/-2)
provider/common/bootstrap_test.go (+1/-1)
provider/common/destroy_test.go (+2/-2)
provider/common/state_test.go (+1/-2)
provider/dummy/config_test.go (+2/-3)
provider/dummy/environs_test.go (+38/-4)
provider/ec2/config_test.go (+3/-4)
provider/ec2/image_test.go (+4/-4)
provider/ec2/live_test.go (+6/-7)
provider/ec2/local_test.go (+11/-9)
provider/joyent/export_test.go (+1/-0)
provider/joyent/joyent_test.go (+0/-1)
provider/joyent/live_test.go (+0/-94)
provider/joyent/local_test.go (+20/-30)
provider/joyent/provider_test.go (+0/-6)
provider/local/local_test.go (+2/-2)
provider/local/prereqs_test.go (+3/-3)
provider/maas/config_test.go (+1/-2)
provider/maas/environ_test.go (+5/-6)
provider/maas/environ_whitebox_test.go (+8/-0)
provider/maas/export_test.go (+64/-0)
provider/maas/maas_test.go (+5/-6)
provider/openstack/live_test.go (+5/-6)
provider/openstack/local_test.go (+15/-22)
testing/base.go (+1/-2)
utils/http.go (+5/-3)
utils/http_test.go (+3/-0)
Changed in juju-core: | |
milestone: | none → 1.16.0 |
Changed in juju-core: | |
milestone: | none → 1.17.0 |
importance: | Critical → High |
tags: | added: test-failure testing |
Changed in juju-core: | |
milestone: | 1.17.0 → 1.19.0 |
summary: |
- cmd/juju ActualRun tests failing on trunk (how!?) + juju test suite should be isolated and do 0% outbound network requests |
summary: |
- juju test suite should be isolated and do 0% outbound network requests + juju test suite should be isolated and do 0 outbound network requests |
Changed in juju-core: | |
milestone: | 1.19.0 → 2.0 |
Changed in juju-core: | |
milestone: | 2.0 → 1.19.3 |
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The code worked before because there wasn't anything in the public s3 bucket for simplestreams data.
Then we uploaded the 1.15 release, and the permissions were wrong, so it searched and some tests started failing. We fixed the permissions, and now the tests that were running are seeing real data and failing.