Travis test setup: address space conflict
Metadata
Current evaluation
Closed without documented resolution. The report detailed a Go runtime address space conflict crashing Travis CI integration tests inside LXD containers. No fix or discussion was recorded, indicating the issue was abandoned or resolved by external infrastructure changes.
Suggested action: —
No scores available.
Issue body
I've seen this a few times now. We're setting Travis up for integration tests, and disaster strikes:
echo "Starting the LXD container."
Starting the LXD container.
# FIXME switch back to unprovileged once LP: #1709536 is fixed
$lxc launch --ephemeral --config security.privileged=true --config security.nesting=true ubuntu:xenial "$name"
Creating test-runner
Starting test-runner
# This is likely needed to wait for systemd in the container to start and get
# an IP, configure DNS. First boot is always a bit slow because cloud-init
# needs to run too.
$lxc exec "$name" -- sh -c "for i in {1..50}; do ping -c1 www.ubuntu.com &> /dev/null && break; done"
sleep 5
$lxc config set "$name" environment.TRAVIS_COMMIT_RANGE "$TRAVIS_COMMIT_RANGE"
runtime: address space conflict: map(0xc820000000) = 0x7f4e9c45d000
fatal error: runtime: address space conflict
runtime stack:
runtime.throw(0xc820241300, 0x1f)
/usr/lib/go-1.6/src/runtime/panic.go:530 +0x92 fp=0x7ffeca228e30 sp=0x7ffeca228e18
runtime.sysMap(0xc820000000, 0x100000, 0x7ffeca228f00, 0xc8204baa18)
/usr/lib/go-1.6/src/runtime/mem_linux.go:210 +0x13a fp=0x7ffeca228e70 sp=0x7ffeca228e30
runtime.(*mheap).sysAlloc(0xc8204a02e0, 0x100000, 0x9c398b31)
/usr/lib/go-1.6/src/runtime/malloc.go:429 +0x193 fp=0x7ffeca228ef8 sp=0x7ffeca228e70
runtime.(*mheap).grow(0xc8204a02e0, 0x8, 0x0)
/usr/lib/go-1.6/src/runtime/mheap.go:651 +0x65 fp=0x7ffeca228f50 sp=0x7ffeca228ef8
runtime.(*mheap).allocSpanLocked(0xc8204a02e0, 0x1, 0x0)
/usr/lib/go-1.6/src/runtime/mheap.go:553 +0x4f8 fp=0x7ffeca228fa8 sp=0x7ffeca228f50
runtime.(*mheap).alloc_m(0xc8204a02e0, 0x1, 0x15, 0xc81fd2e6cc)
/usr/lib/go-1.6/src/runtime/mheap.go:437 +0x11d fp=0x7ffeca228fd8 sp=0x7ffeca228fa8
runtime.(*mheap).alloc.func1()
/usr/lib/go-1.6/src/runtime/mheap.go:502 +0x43 fp=0x7ffeca229008 sp=0x7ffeca228fd8
runtime.systemstack(0x7ffeca229028)
/usr/lib/go-1.6/src/runtime/asm_amd64.s:307 +0xa1 fp=0x7ffeca229010 sp=0x7ffeca229008
runtime.(*mheap).alloc(0xc8204a02e0, 0x1, 0x10000000015, 0xc81f89f328)
/usr/lib/go-1.6/src/runtime/mheap.go:503 +0x65 fp=0x7ffeca229058 sp=0x7ffeca229010
runtime.(*mcentral).grow(0xc8204a1ee0, 0x0)
/usr/lib/go-1.6/src/runtime/mcentral.go:209 +0x95 fp=0x7ffeca2290c0 sp=0x7ffeca229058
runtime.(*mcentral).cacheSpan(0xc8204a1ee0, 0xc82049a898)
/usr/lib/go-1.6/src/runtime/mcentral.go:89 +0x47f fp=0x7ffeca229100 sp=0x7ffeca2290c0
runtime.(*mcache).refill(0x7f4e9c55d000, 0x7f4e00000015, 0x7ffeca229168)
/usr/lib/go-1.6/src/runtime/mcache.go:119 +0xd0 fp=0x7ffeca229138 sp=0x7ffeca229100
runtime.mallocgc.func2()
/usr/lib/go-1.6/src/runtime/malloc.go:642 +0x2d fp=0x7ffeca229158 sp=0x7ffeca229138
runtime.systemstack(0x7ffeca2291f8)
/usr/lib/go-1.6/src/runtime/asm_amd64.s:307 +0xa1 fp=0x7ffeca229160 sp=0x7ffeca229158
runtime.mallocgc(0x180, 0xc8201a2380, 0x0, 0x800000000)
/usr/lib/go-1.6/src/runtime/malloc.go:643 +0x87c fp=0x7ffeca229238 sp=0x7ffeca229160
runtime.newobject(0xc8201a2380, 0xc82049aff0)
/usr/lib/go-1.6/src/runtime/malloc.go:781 +0x44 fp=0x7ffeca229260 sp=0x7ffeca229238
runtime.malg(0xc800008000, 0xc82049b3a0)
/usr/lib/go-1.6/src/runtime/proc.go:2634 +0x29 fp=0x7ffeca229298 sp=0x7ffeca229260
runtime.mpreinit(0xc82049bb60)
/usr/lib/go-1.6/src/runtime/os1_linux.go:205 +0x21 fp=0x7ffeca2292b0 sp=0x7ffeca229298
runtime.mcommoninit(0xc82049bb60)
/usr/lib/go-1.6/src/runtime/proc.go:494 +0x109 fp=0x7ffeca2292f8 sp=0x7ffeca2292b0
runtime.schedinit()
/usr/lib/go-1.6/src/runtime/proc.go:434 +0x7d fp=0x7ffeca229340 sp=0x7ffeca2292f8
runtime.rt0_go(0x7ffeca229448, 0x6, 0x7ffeca229448, 0x0, 0x7f4e9bdc8f45, 0x0, 0x7ffeca229448, 0x600000000, 0xc81f8ee9b0, 0x0, ...)
/usr/lib/go-1.6/src/runtime/asm_amd64.s:138 +0x134 fp=0x7ffeca229348 sp=0x7ffeca229340
The command "sudo ./tools/travis/run_tests.sh integration" exited with 2.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without documented resolution. The report detailed a Go runtime address space conflict crashing Travis CI integration tests inside LXD containers. No fix or discussion was recorded, indicating the issue was abandoned or resolved by external infrastructure changes. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
20
|
close stale | Travis CI integration test setup fails with a Go 1.6 runtime address space conflict during LXD container initialization. No maintainer response or activity in over 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
5
|
close stale | Travis CI integration tests fail with a Go 1.6 runtime address space conflict during LXD container setup. Issue is 8+ years old with no maintainer interaction or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
95
Support Request:
10
|
close stale | CI integration test failure caused by a Go 1.6 runtime address space conflict inside an LXD container. The issue is over 8 years old, has no maintainer interaction, and relies on completely deprecated infrastructure and OS versions. | |
| qwen3.6-35b-moe-q4 |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Integration tests fail with a Go 1.6 runtime address space conflict during Travis CI LXD container setup. No maintainer response or activity in over 8 years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2149 travis: use LXD from 3.0 track | snapcraft | merged | Merged Travis CI configuration update switching to the LXD 3.0 track and removing the obsolete testbr0 setup. This resolves build failures caused by recent LXD networking changes. Approved by reviewer and passed CI checks. |